Jump to content

aptalca

Community Developer
 View Profile  See their activity

  • Posts

    3,064

  • Joined

  • Last visited

  • Days Won

    3

 Content Type 

Everything posted by aptalca

  1. aptalca
  2. aptalca
    It's all explained in the docker image description on both github and docker hub
  3. aptalca
    Read 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 apps
  4. aptalca
    Hi, 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. Thanks
  5. aptalca
    That's the docker network ip. You can use the host ip instead and it should work
  6. aptalca
    Check out the preset conf for unifi. I imagine you need something similar
  7. aptalca
    There 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?
  8. aptalca
    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.
  9. aptalca
    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.
  10. aptalca
    Port should be 8080 and make sure both jira and letsencrypt are in the same "user defined bridge" network
  11. aptalca
    Reply 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.
  12. aptalca
    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 cloudflare
  13. aptalca
    You shouldn't be changing certificate locations. Container handles them automatically through symlinks. Leave them as default.
  14. aptalca
    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.
  15. aptalca
    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 connection
  16. aptalca
    Brackets mean "replace with your username" rather than literally typing "username"
  17. aptalca
    Uppercase doesn't work in dns hostnames in nginx. Change GitLab-CE to all lowercase or use the ip instead
  18. aptalca
    I connect 2 devices through the same user account on a daily basis. It must be the settings.
  19. aptalca
    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.
  20. aptalca
    Init file runs during container start. So you can put "apk add --no-cache sslh" in there and it will install if necessary during every container start.
  21. aptalca
    Not willing to route everything through sslh. You can add it yourself via mapping an init file into the /etc/cont-init.d folder
  22. aptalca
    I believe that's a known plex issue. There are a few threads on their forum about it
  23. aptalca
    It looks like there is an invisible/blank character before that return. Did you copy paste from somewhere? Try removing that and restart the container
  24. aptalca
    Not enough info to go on
  25. aptalca
    You can always pull the official php images (whichever version you need) and point the nginx fcgi parameter to the php container's ip address
×
×
  • Create New...