ofthethorn

I sorted it out. Downgrade to version 132 and everything works flawlessly. Edit: You do this by going to your Ombi container. Make sure you are on advanced view! Then, where it says repository add :132 behind the existing text so it looks like this: linuxserver/ombi:132

Hello, Last night everything was working perfectly fine, however since this morning I seem to be unable to login. I am running Ombi behind a reverse proxy and am using a DuckDNS domain to access it. As mentioned, everything was working flawlessly before this morning. I am unaware of any changes performed on the container (currently not at my place and I do not have access to the unRAID webUI). Maybe Ombi updated itself causing this issue? Anyhow, I can still access the domain, and when I enter an incorrect username/password I get an error. However, upon entering correct credentials nothing happens. I looked through console and found that token/ seems to be causing an error: " SQLite Error 5: 'database is locked' ". Plex is still accessible through duckDNS domains btw. Any tips on fixing this?

I got it. I got stuck after doing what you described. I, like a complete dummy, forgot to change the plex conf file. Got it all working. Thanks for all the help man.

I'll look into it when I get back home. I'll let you know how it goes! Thanks for all the help though.

Another quick update: since my router is a piece of trash I cannot control (forced by ISP) I decided to just add a second plex container, change its name and give it its own appdata folder. This container will solely be used for local access and is not setup in the LE docker. This won't have any downsides I hope... Thanks for all your help though! Really appreciate the effort.

That sorted it.

That may actually be it. I followed spaceinvader one's guide, I believe. And he recommended making a new docker network.

Port 32400 is closed, so that's a negative. Plex is on a separate network, the same as duckDNS and Le.

All seems to work now. Alas, still no connection to the local server. Probably should've added that I can't even connect to plex docker IP address.

Dumb question probably, and thanks for all your help. But which line would that be?

I get this: nginx: [emerg] the size 10485760 of shared memory zone "SSL" conflicts with already declared size 52428800 in /config/nginx/proxy-confs/plex.subdomain.conf:3 Error

Thanks! Any quick method to copy and paste this? Doesn't seem to work with Krusader.

On it. Is this what you mean? https://imgur.com/a/NDRj9Sn

Doesn't seem like my router has the capability to do so... Would running a second Plex container work? Exclusively for local network and not hidden behind a reverse proxy?

I assume this is the right place to post this. First of all, love all the work that has been done for the dockers. They are truly amazing. I finally got everything running and can remotely connect into my server. I have an issue though. I cannot connect to my server locally, only remotely. Do I have to change a setting in the letsencrypt docker to enable this? Thanks in advance, Thorn