Jump to content

EvilNuff

Members
  • Posts

    3
  • Joined

  • Last visited

Posts posted by EvilNuff

  1. On 9/11/2022 at 6:41 PM, Xcelsior86 said:

    Just installed this today and for whatever reason, the docker icons themselves are changed to the icon I'm using for the folder itself.  I've tried everything in the settings and nothings seems to get the regular icons back other than removing the icon I set for the folder.  Anyone else run into this issue?

    I am having the same problem with 6.10.3.  Turning off "Only animate icon on hover:" fixed the icon problem for me.

     

  2. Greetings, not really sure how to troubleshoot my problem so any help is appreciated.  I had letsencrypt set up with my registered domain and reverse proxies working with 3 docker containers (calibre-web is one).  Sometime in the past couple days it stopped working.  I am getting a site cannot be reached error and port 443 is no longer showing open for me.  Checking the letsencrypt logs I see this:

    Quote

     

    nginx: [emerg] unknown "upstream_protop" variable
    nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)

    Repeated endlessly.  I glanced at my pihole and see that my unraid server is spamming ocsp.int-x3.letsencrypt.org about 2500 times every 10 minutes since yesterday.  That's about 4 times a second.  Some googling on that error essentially tells me to ignore it and letsencrypt still works fine.  

     

    My port forwarding has not changed, I have not touched the configs for letsencrypt, etc.  My best guess is something stopped nginx from serving up the sites and thus the ports are not showing open.  I am not sure where else to look for how to resolve this issue?  Thanks.

     

    Edit: 
    Found the problem, there was a typo aka user error in one of the conf files.  I had replaced http with $upstream_proto in one of the conf files and had a typo such that the p from http was still there.  Sorry for the distraction!

×
×
  • Create New...