saarg

Blank page is usually an add-on blocking something.

You set it to the host IP address, the same as unraid. If you are not using the standard port, that might be the reason you have issues.

Yes. Plex will download it again when you restart the container.

I don't think they have tried to go headless at all. Headless have been hacks from the start I think. I would go emby until jellfish is stable enough. If you only use the emby for kodi plugin you don't need premium. Well, maybe if you want hardware acceleration.

Did you try to clean out the codecs folder and restart plex?

It's still maintained, so no worries for the future. But I would reccomend switching to emby/jellyfin as the backend. Much easier setup and it's not a hack. And you also get the plugins for Kodi to integrate the library.

I just did a new installation of Nextcloud here and do not have that error message. I can see from the proxy-conf you posted above that you have edited it. Do not do that. Do only what is mentioned in the top of that file. How does your default file in nextcloud look like?

Delete this file appdata/nginx/site-confs/default in nextcloud appdata and restart the nextcloud container. The solution was found as the first hit on google if you would have googled sameorigin nextcloud linuxserver.

It might be the ssl.conf or the proxy.conf that needs updating. Check the date at the top with the one on GitHub. If they are different, delete them and restart the container.

Fresh install, so the appdata folder was never used before? If that is the case, then you might need to update your reverse proxy conf. Delete the nextcloud sample and restart letsencrypt. That will restore the newest sample. Then edit the sample as instructed at the top of the file, save it and delete the old proxy conf file. Then remove the sample part from the filename and restart letsencrypt.

I'm sorry we have a life outside of linuxserver.

I'm talking about the settings in letsencrypt and not port forwarding. I don't know how spaceinvader tells you to set it up, so you should go back and make sure you did it correctly.

Letsencrypt I would say. If you follow the readme in the proxy-confs folder and the info at the top of the proxy-conf file you use it's not hard to get it to work. You have followed some guide you found on the internet and then copy/pasted it in the various config files?

You have configured something wrong.

You don't have to uncomment anything in the default file to get it working.

You can access it via the IP, but you will be redirected to the domain when the page loads.

When you update the container you update everything except nextcloud. So is pacakges and dependencies. Update the container first, then nextcloud.

You are messing around with settings you don't need to change. There is no mention of changing the port in the proxy conf, so that means don't change the port! It's talking on the internal docker network, so port mapping doesn't apply. 443 is the correct port. Leave the nextcloud config at 444, as that is for accessing locally using IP. As for the default file you keep on insisting to edit, don't! There is nothing you have to comment or uncomment to make either subdomain or subfolder working.

You said you were running it on a single core VPS and I don't see how you can run unraid on a VPS as you need a usb drive for unraids license. I think letsencrypt tries to renew when it's less than 30 days before the cert expires.

If you are not using unraid, this is not the right place for support. Use our discourse or discord. Letsencrypt needs to run if the cert is to be renewed. The check is scheduled to run at night at around 2.

Didn't see it was commented out. You have created a custom network that both nextcloud and letsencrypt use, right? If so you have not followed the instructions at the top of the proxy conf. You have changed the port from 443 to 444. That is something you should not do. Change it back to 443 and restart letsencrypt.

Isn't it easier to just reverse proxy nextcloud using the letsencrypt container? That way you can have both running at the same time and you don't have to copy any certs or expose ports for nextcloud.

If I open the same folder again, it opens the files I had opened before closing the browser. I think.....

Remove the one you added. There is no need to edit anything in the default file to get proxy confs working. All you have to do is to remove the .sample part, edit the file if it is mentioned to do so in the top of the file and restart letsencrypt. Did you restart letsencrypt?

I even quoted you the text from the first post and where to click in that text to get to the post describing the command to update.