Closed IevgenSobko closed 10 months ago
Which proxy conf is this about? I don't see one for fileserver
Ups, sorry, my bad. Was in hurry and made mistake. I meant Filebrowser. Let me edit the issue.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
I had this same problem -- switching the ports from 8080 to 80 fixed it.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Lets hope pull request will be accepted.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
This issue is locked due to inactivity
Is there an existing issue for this?
Current Behavior
Currently, 8080 port used in proxy file configuration, so you need to go and change it to default 80
Expected Behavior
Proxy should work without need to go and change port from 8080 to 80 in proxy configuration file
Steps To Reproduce
Even if you deploy filebrowser container and try to change port to 8080 default healthcheck from image will ping 80 port
Failed to connect to localhost port 80 after 0 ms: Connection refused