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
    Open your domain in a better and click on the lock to see if it really expired If so, check the log in the config folder under letsencrypt to see why the renewal failed
  2. aptalca
    Then check your port forwarding and post your docker log here
  3. aptalca
    Your db was likely already corrupted before the switch. Google how to restore Plex db
  4. aptalca
    Move the config folder to /mnt/cache or /mnt/diskX if it's not there already
  5. aptalca
    How about port 80 tcp? A lot of public wifi also block vpns (mainly block all udp connections as well as tcp except for 80 and 443) so I use port 80 for mine
  6. aptalca
    Switch to bridge networking and some other changes. See the GitHub or docker hub pages for specific info (links on the first page)
  7. aptalca
    Just the naked domain will suffice, without /admin at the end This is all in official openvpn-as documentation by the way
  8. aptalca
    There is a separate thread for discussing the script as it's not published by the lsio team. In your screenshot, you see hw next to the encode portion (h264 after the arrow), but no hw next to decode (h264 before the arrow)
  9. aptalca
    What about https://domain.com ? From outside your wan like on a phone with cell connection
  10. aptalca
    Define not working
  11. aptalca
    You have some incorrect port forwards. For starters, your outside port 443 has two rules trying to forward it to different ports. And some have the outside and inside ports switched. It should go from 80 to 81 not the other way around
  12. aptalca
    Your encode is hw, but the decode is sw
  13. aptalca
    In your sonarr container settings, open advanced and into extra arguments enter --network-alias=sonarr
  14. aptalca
    If you need help with troubleshooting, start with posting your docker log Also, it's not a good idea to test a reverse proxy right off the bat. Set up the container first, check the logs to make sure the certs are retrieved correctly. Then test to make sure you can get to the placeholder homepage. Only then you should test the reverse proxy. Step by step. And here's a detailed guide that covers many scenarios: https://blog.linuxserver.io/2019/04/25/letsencrypt-nginx-starter-guide/
  15. aptalca
    I meant force refresh your browser. Ctrl-F5
  16. aptalca
    Force refresh
  17. aptalca
    You forgot to rename the second variable name in your works one. Fix the last line for proxy pass
  18. aptalca
    Post the new confs you're using and check the error log in the config folder
  19. aptalca
    Try changing the variable name to upstream_nextcloud_works
  20. aptalca
    You can do so through the plug-in. Select a stock build
  21. aptalca
    Return all those values to the defaults. Only add your lan subnet to the routing section
  22. aptalca
    Perhaps read the documentation? On github or docker hub
  23. aptalca
    Download a new client config. Your current config was generated before you fixed the hostname on your server.
  24. aptalca
    Nope. Certbot added an up to 10 minute delay to renewal attempts so no more renewals during container start. Only via cron
  25. aptalca
    Provide more clarification
×
×
  • Create New...