Unable to change https port
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I have a brand new install, 5.9.9, and when changing the https port then rebooting the controller will not longer start. I have seen many other threads on here and the only way to fix this is to modify entries in mongo and the omada.properties file does nothing.
I should mention I have attempted the install on older versions as well, with no luck, Is there a way to get port 443 working on this?>
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
TP-Link got back with me and sent this on how to fix the controller without reinstalling / modifying the DB.. Also the reason behind not being able to use 443, I think there should be a dissclaimer as if you choose 443 then it might not work.. anywho..
https://www.tp-link.com/us/support/faq/3429/
- Copy Link
- Report Inappropriate Content
it seems it does not work at all. changing that makes no difference. i am able to reach localhost by default 8043.
maybe it's a bug or, maybe cache?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
For what it is worth.. I am attempting to put this site behind cloudflare, cause you know people.. anywho.. Since I am unable to modify the port to 443 I am unable to..
Cloudflare does not support port 8043 with the free version..
HTTPS ports supported by Cloudflare 443 2053 2083 2087 2096 8443
How to enable Cloudflare’s proxy for additional ports:
If traffic for your domain is destined for a different port than the ones listed above, for example you have an SSH server that listens for incoming connections on port 22, either:
Change your subdomain to be grey clouded via your Cloudflare DNS app, to bypass the Cloudflare network and connect directly to your origin.
Configure a spectrum applicatioin for the hostname running the server. Spectrum supports all ports. Spectrum for all TCP and UDP ports is only available on the Enterprise plan. If you would like to know more about Cloudflare plans, please reach out to your Cloudflare account team.
- Copy Link
- Report Inappropriate Content
@Myk3 Since 5.9.9 is only out for Windows and Linux at this time, I'm confused as to why you can't do some simple port changing either at the OS or firewall level.
What OS are you using for your controller, and is your controller platform seriously connected directly to the internet? Perhaps it is cloud hosted?
EDIT for that matter, why not just use TPlink's own free cloud access platform?
- Copy Link
- Report Inappropriate Content
yeah, system is a VPS hosted in the cloud.. I have limited it to only accessable through the ufw firewall, so it should be somewhat protected.. at least it will be once I get the port stuff figured out..
- Copy Link
- Report Inappropriate Content
Ok, so one VPS provider I looked at, 'vultr' supports a variety of OS and some one click applications, one of which is Docker. So why not run your controller as a Docker container and use that to remap ports between the container and the host IPs? I've been running 5.9.9 in a Docker container on my NAS (albeit with host networking), but it should be trivial to do a 1:1 NAT for the required ports and then you can get on with your design.
- Copy Link
- Report Inappropriate Content
For what it is worth, I was able to change the default port to 8443 and everything is working.. I have the firewall setup to only allow connections through cloudflare, which should givve me a decent level of protection..
- Copy Link
- Report Inappropriate Content
TP-Link got back with me and sent this on how to fix the controller without reinstalling / modifying the DB.. Also the reason behind not being able to use 443, I think there should be a dissclaimer as if you choose 443 then it might not work.. anywho..
https://www.tp-link.com/us/support/faq/3429/
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1014
Replies: 9
Voters 0
No one has voted for it yet.