-
Notifications
You must be signed in to change notification settings - Fork 199
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
[BUG] - POrt 80 is opened with forward to port 443 by default with no ability to remove this #474
Comments
Hi @GRIFFCOMMca I just reviewed the code and that is the default behavior of Zoraxy. I consider this a feature (less setup steps from user perspective) instead of a bug. If you want that default value to be changed, there are two ways you can achieve that
|
We are using the Windows version, there is no way to edit the code, i feel this should be listed in the panel as you suggested so it can then be removed. Most services this will sit in front of will have port 80 in use and make using this software impossible... |
@GRIFFCOMMca You can temporary shut down the port 80 service and setup Zoraxy, or even change the setting in another machine and copy the whole folder structure over to your homelab gateway server. There are lots of way to do the same desired results you are expecting and I don't see a problem here. And btw, Golang do have a Windows compiler where you can build the whole code base on Windows and deploy on Windows. Checkout here and README build from source instruction for more details. |
Hi, going to review this later today, there are some examples though where port 80 on the original install isnt possible, in this case in maybe, i did not see this setting, will respond here in a few hours. |
This is interesting, in that area (Status > Global settings) both Enable HTTP server on port 80 AND Force redirect HTTP to HTTPS were both off... i had to enable both then disabled them again for this to work.. so according to my GUI they were off (disabled), however the backend server was doing them even though the GUI said they were not.. |
This is now working, however bug still exists in that the settings you showed are not shown as ACTIVE when installed while they are active in the live server, they both need to flipped off and back on to reflect the real status, then then allows them to be turned off |
The UI bug cannot reproduce on my side, but I have optimized this a bit further for beginners.
|
This is the first time I'm trying to use zoraxy. I stopped the service as advised with /etc/init.d/uhttpd stop After that, zoraxy starts as expected. But I got the same effect as @GRIFFCOMMca
Maybe it could make sense to have a additional option parm to disable redirect when starting zoraxy. |
@fow0ryl This has been fixed in the dev branch and will be releasing with 3.1.7. In the dev version, it will automatically disable port redirect if the 80 port is occupied by another process. |
Describe the bug
On starting the application (for Windows) port 80 has a service running which forwards to port 443, no way to delete / turn off or stop it happening.
To Reproduce
Run the application in Windows, open a webpage to http://localhost
Expected behavior
Should not start any servers on any ports other than the admin server port, unless created
Screenshots
Host Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: