aptalca
Community Developer
-
Joined
-
Last visited
Everything posted by aptalca
-
I don't know why or where you're using an .htaccess file but that's likely your issue. You need to pass ports 443 and 80 to the letsencrypt container unaltered. Browser thing is just a cache issue. 301 redirects are permanently cached
-
Based on the error, it seems your port 80 is not correctly forwarded by your router to this container
-
Post your container log and the container settings
-
Don't do host networking
-
Post your container settings
-
Php is enabled by default. Make sure your php block is still enabled in your default site config
-
Nginx reverse proxy is the right way for that. Check out the letsencrypt image. It works with duckdns
-
It's all explained in the docker image description on both github and docker hubRead the info at the top of the preset proxy conf. It tells you how to enter the domain url in plex settings so it is reachable via apps.plex.tv and in mobile appsHi, We use custom networks (user defined bridge network) for docker containers for container to container direct connections with name resolution. One can manually create a user defined bridge network and it is available as an option under network in container settings. That part works great. However, if that custom network is selected, when one tries to add a port mapping, there is no option for "container port", but only host port and other fields like name and description. To reproduce, pick any docker template (preferably one in host mode), switch it to the custom network and add a port mapping. You'll see that the container port option does not exist. To work around it, one has to select "bridge" first, add the port mappings, and then switch back to the custom network. ThanksCheck out the preset conf for unifi. I imagine you need something similarThere is log rotation, it shouldn't have gotten that big. It rotates weekly and gzips all but the last two Did you modify the crontab?Sure, it is. The container by default is connecting to php via ip address already. It doesn't really matter whether the php/fcgi service is running in the same container or somewhere else, as long as the ip address is reachable.You changed the host port. The container port is still 8080. Nginx is connecting directly to the container via docker network, not going through host. Use 8080 in the proxy pass statement.Port should be 8080 and make sure both jira and letsencrypt are in the same "user defined bridge" networkReply about dns validation was to someone else, not you. ssl.conf already defines the certs. You don't have to do that manually. I don't know where you got those two lines from.Currently, no support for dns validation with duckdns. I recommend looking on namecheap, getting one with the lowest annual renewal (there were some $4/yr ones last I checked) and setting it up with cloudflareYou shouldn't be changing certificate locations. Container handles them automatically through symlinks. Leave them as default.They are either or. If you do user defined bridge, don't modify the proxy conf and it should work (after you enable it by renaming). If you do host networking or macvlan, replace the container name with the ip address. What you tried to do above was mixing and matching. You had user defined bridge network, but you also tried to connect via ip of the host. However, because you did not map the container port on the host port, connection through host ip did not work.If you do user defined bridge, you should use the proxy conf as is, without replacing the container name with the ip address. You are trying to proxy through ip, but you didn't map any ports, so no connectionBrackets mean "replace with your username" rather than literally typing "username"Uppercase doesn't work in dns hostnames in nginx. Change GitLab-CE to all lowercase or use the ip insteadI connect 2 devices through the same user account on a daily basis. It must be the settings.I don't think it's two concurrent connections, but two concurrent users. You can have multiple devices/connections using the same user account. Iirc I tried connecting with 3 devices at the same time all using the same account and it was fine.
