![]() ![]() I went around this by using 9090:443 and pointing 443 to 9090 on my router. I even went in netstat -ano | findstr :80 and 443Ĭ:\Users\Administrator>taskkill /pid 4 /FĮRROR: The process with PID 4 could not be terminated. PS G:\servers\nginx-swag> docker-compose up -dĮRROR: for reverseproxy Cannot start service reverseproxy: Ports are not available: listen tcp 0.0.0.0:443: bind: An attempt was made to access a socket in a way forbidden by its access permissions.ĮRROR: Encountered errors while bringing up the project. PS C:\Users\Administrator> cd G:\servers\nginx-swag Either you plonk in your currentl nginx configuration in the block with listen 443 or you proxy to Trying to compose this with 80 and 443 errors even in admin PS You shoudl also then have a file in /path/to/config/nginx/site-confs/default where you can edit what you want to proxy to do. The linuxserver container should immidiately give you a default https site available on port 443 (test if that works). one for the website, one for nextcloud and whatever else you want. You can also remove the nginx container (or keep it your choice), it´s not strictly speaking necessarly (since the other one includes nginx too), but if you want to segregate tasks/configuration in some way you can also keep it and reverse proxy only and have other containers that each host some site you have. So in your case your current nginx container would have been reachable by from other containers defined in the same file, there is no need to forwards the port. If you create your nextcloud container in that same file docker-compose will create a dns alias with your container name. Remove all the ports from all other containers that you defined in that file. But i think those are the most essential to get it working at all. There is a lot more configuration that you can do in there look up their documentation for more details. # - SUBDOMAINS=www, <- optional list for sub-domains Add a service like this to your compose file.I just tried this out locally to see if the docker-compose file was valid that i was creating, though I don´t have a domain pointing to my desktop so not 100% sure it works. You just have to add what you want it to do. You don´t have to bother creating and renewing the SSL cert. Though, looking at this there is actually much less to do as everything is pre-configured. ![]() I´ve also setup a bunch of nginx as a reverse proxy and for SSL before, but never with docker (I just installed nginx on those systems and configured SSL there). But I´ve used some of the linuxserver.io images for other things and they where pretty solid, so I would recommend you try this one linuxserver/swag. ![]() I´ve never done this specific thing with docker. ![]()
0 Comments
Leave a Reply. |