-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Configurable HTTP webserver port #573
Comments
Another option can be to use apache on a Linux host and let Apache do the "port translation" via a proxypass directive. e.g. bla1.mydomain.com and bla2.mydomain.com can all be pointing to the same A-record of your router and all use port 80. Apache will then route to the proper host internally, based on the domainname in your browser's URL. This can be as simple as a Raspberry pi or any other Linux host. |
I have done the hidden some devices behind a proxy, but there are a few URL that are a few Absolute URLs in the ESPEasy firmware - https://www.letscontrolit.com/forum/viewtopic.php?f=4&t=3628 I can detail how to do this for hostname, subdomains and sub URLs, if anybody is interested. |
I was thinking of another advantage of using Apache as a proxy. You simply do not want ESPeasy to be accessible via the internet without some minimal protection. @LeeNX how can the URLs be absolute (with included hostname)? |
I have secured a domain with an SSL and used OAuth for access, using a single domain, with sub-URL for different devices. https://espeasy.leenx.lan/ESP-01/ and https://espeasy.leenx.lan/ESP-02/ ... but if you click something like reboot, the URL looks like https://espeasy.leenx.lan/reboot, instead of https://espeasy.leenx.lan/ESP-01/reboot. Agreed, if you use the honstames as in https://esp-01.espeasy.leenx.lan and https://esp-02.espeasy.leenx.lan, this would not be a problem. |
Ah, I get it now. |
any news on this? HTTP port setting would be a nice feature. |
It would also be nice to be able to set the web page username - a bit more secure that just "admin" |
@LeeNX @TungstenE2 @ghtester so if you want to test it maybe we can ask @TD-er to provide test builds :) |
I'm glad that you are happy :) |
Thanks again for a great work, this thread can be closed. :-) |
I think it would be nice if the default HTTP port could be easily configurable in the webserver settings please. AFAIK, currently it is "hardcoded" in source file ESPEasy.ino :
// WebServer
ESP8266WebServer WebServer(80);
As I would like to get several ESPEasy devices temporarily accessible behind my old router (which can support only 1:1 port forwarding), it's not easily possible when all ESPEasy webservers can listen only on the same port 80.
By the way, thanks a lot to all contributors of this great project. It's a really good work!
The text was updated successfully, but these errors were encountered: