onsolutionjames
commented
2 years ago Hi @ymgupta. I've been having similar issues with LNS on port 443 - I think it's two main things, see my existing Github issues and proposed fixes here:
- Main issue: https://github.com/TheThingsNetwork/lorawan-stack/issues/5197
- Related, but non-critical issue: https://github.com/TheThingsNetwork/lorawan-stack/issues/5198
So from my testing I can get it to work on 443 on a local install, however a The Things Industries support person has suggested that they don't support LNS on port 443 for TTS Cloud and TTS Community Edition. See this thread for some history.
See this specific reply in the forum about what you need to configure in your server/reverse-proxy to get it to work for self-hosted installs.
Perhaps after my fixes have gone through, they can make the additional changes needed that @htdvisser suggested in the forum (my guess is some kind of config changes to the Envoy proxy that they use?)
KrishnaIyer
Summary
TTS Cloud and TTS Community Edition support connecting LBS gateways in LNS mode on port
443. But, there is a bug on The Things Stack end that needs to be fixed to get this working.Previous Context: https://github.com/TheThingsIndustries/lorawan-stack-support/issues/724
Steps to Reproduce
wss://<server-address>:443What do you see now?
8887. But, haven’t had any success getting LNS to work on port443.2022-02-08 03:49:12.153 [AIO:ERRO] [3] WS upgrade failed with HTTP status code: 403errors in the station logs when the port is configured as443.What do you want to see instead?
Connect LBS gateway to TTS cloud in LNS mode on port 443.
Environment
TTS v3.18.1
How do you propose to implement this?
...
How do you propose to test this?
...
Can you do this yourself and submit a Pull Request?
No.