[GH-ISSUE #11] Does it use HTTPS? #12

New issue

Closed

opened 2026-03-02 23:32:57 +03:00 by kerem · 5 comments

kerem commented

2026-03-02 23:32:57 +03:00

Owner

Originally created by @shreyasajj on GitHub (Jun 13, 2022).
Original GitHub issue: https://github.com/airmessage/airmessage-server/issues/11

Im trying to add my own reverse proxy on it and the server refuses to work the same way as when i connect to directly to ip address.
Example 192.168.1.90:1359 works fine but airmessage.example.com does not and airmessage.example.com points to http://192.168.1.90:1359. So im a little confused why?

Originally created by @shreyasajj on GitHub (Jun 13, 2022). Original GitHub issue: https://github.com/airmessage/airmessage-server/issues/11 Im trying to add my own reverse proxy on it and the server refuses to work the same way as when i connect to directly to ip address. Example 192.168.1.90:1359 works fine but airmessage.example.com does not and airmessage.example.com points to http://192.168.1.90:1359. So im a little confused why?

kerem closed this issue

2026-03-02 23:32:57 +03:00

kerem commented

2026-03-02 23:32:58 +03:00

Author

Owner

@larsdennert commented on GitHub (Jun 14, 2022):

This is not the appropriate place to ask questions. Use https://www.reddit.com/r/AirMessage/ and even that is not relevant to a local dns service on a LAN having to do with AirMessage.

@larsdennert commented on GitHub (Jun 14, 2022): This is not the appropriate place to ask questions. Use https://www.reddit.com/r/AirMessage/ and even that is not relevant to a local dns service on a LAN having to do with AirMessage.

kerem commented

2026-03-02 23:32:58 +03:00

Author

Owner

@shreyasajj commented on GitHub (Jun 17, 2022):

Um this is not on local dns service, the dns service works fine, however it seems that the client wont connect to the backend if the project is upgraded to https for some reason. It like the app cannot use https to verify and implement encrypted tunnel transport

@shreyasajj commented on GitHub (Jun 17, 2022): Um this is not on local dns service, the dns service works fine, however it seems that the client wont connect to the backend if the project is upgraded to https for some reason. It like the app cannot use https to verify and implement encrypted tunnel transport

kerem commented

2026-03-02 23:32:58 +03:00

Author

Owner

@tagavari commented on GitHub (Jun 18, 2022):

AirMessage does not use HTTPS. Instead, it uses a custom protocol built on top of TCP, which also handles data encryption.

@tagavari commented on GitHub (Jun 18, 2022): AirMessage does not use HTTPS. Instead, it uses a custom protocol built on top of TCP, which also handles data encryption.

kerem commented

2026-03-02 23:32:58 +03:00

Author

Owner

@shreyasajj commented on GitHub (Jun 20, 2022):

Ah I see, It need a tcp router work for this, I assume so. Using Traefik

@shreyasajj commented on GitHub (Jun 20, 2022): Ah I see, It need a tcp router work for this, I assume so. Using Traefik

kerem commented

2026-03-02 23:32:58 +03:00

Author

Owner

@MrOwen commented on GitHub (Jul 22, 2022):

@shreyasajj about to set this up. When you set up your TCP router, did you enable TLS, enable TLS with passthrough, or no TLS? And if you used TLS or TLS with passthrough, what did you use for the matching? HostSNI(`*`) or HostSNI(`airmessage.example.com`)?

@MrOwen commented on GitHub (Jul 22, 2022): @shreyasajj about to set this up. When you set up your TCP router, did you enable TLS, enable TLS with passthrough, or no TLS? And if you used TLS or TLS with passthrough, what did you use for the matching? ``HostSNI(`*`)`` or ``HostSNI(`airmessage.example.com`)``?

kerem referenced this issue

2026-03-13 20:01:31 +03:00

[GH-ISSUE #12] TIFF Image Support #8