saarg

I was answering the last line. There will be a new template when we get around to it. The container still works, so no need to panic.

There is nothing different except the name.

That depends on how long it is since you updated nextcloud. If you lag too far behind on nextcloud, you will get problems updating the container as dependencies will be updated.

This is not related to this container, so I suggest you create your own thread about corrupt cache drive. This is most likely a hardware issue and this container did not break anything.

That is correct. You also need a subdomain for it on your domain if you are not using wildcard cert.

If you already have SWAG, just enable the subdomain conf for code-server.

Heimdall is still alive. You are probably talking about the update ready/up to date/not available on the untaid docker page? If so, that is an unraid issue and nothing to do with the container. You can try a force update and see if that works.

Only edit the one in /config. Do not use the others you may have found.

You should set use cache: only That is most likely your problem. You also need to check on which drives the date is on so you can move it.

The one in the /config folder gets copied to the correct location.

Doesn't look like you have followed the instructions posted on the forum about using the igpu. You are missing to change permissions on /dev/dri.

That just shows files on the cache disk. It doesn't mean there is no files on the array. Check the share settings and also click the browse icon on the share to see which drives the files reside on.

Have you tried with an empty appdata folder? Might be something corrupted in your appdata.

It's probably caused by the self signed cert. You need to add the address to the safelist. Some browsers let you accept the risk and go to the address.

Are you absolutely sure it's on the ssd? It sounds like it's on a spinner and it spins up.

Not sure what you mean? Nginx is the reverse proxy, so you don't need to proxy nginx. If you are using the nginx container, you can just move the site the letsencrypt container as it is the same. The difference is certbot.

You have not cleared the appdata if you get the login page.

If you didn't go through the setup, you have already set it up at an earlier point.

You can't without changing the run file inside the container. And it will be overwritten every time you update the container.

Post your docker run command and the IP:port you are using to access calibre.

He said he was using DNS verification, so he don't need port 80. And this belongs in the correct thread, not here.

Normally, but I don't know about next nextcloud. The database depends on the setup. If you use an external database, it will be in that softwares appdata and if you use sqlite, please don't as it's slooow, it's in the data volume.

They have probably changed stuff, but forgot to change it in the wiki. I have not tested it here, just know it from emby.

What do you see?

Click on the letsencrypt container and choose command line. Then run the following command: ping nextcloud You are trying https://yourdomain.com right?