saarg

There is no default username/password for this container. And what is Yacy?

It only create one cert covering everything.

It's not integrated. It has the config files to use authelia. Follow the guide on our blog to set it up. https://blog.linuxserver.io

It's still maintained. See here https://github.com/linuxserver/docker-kodi-headless/issues/112

Follow this https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/

You have to fix your port forward or whatever it is that is blocking the connection.

No you can't, as nginx isn't started until you have a valid cert.

No it's not.

What do you mean by next? You only have stable and beta channel in the webui. There is info on updating using the command line in the first post.

It's the window that pops up when you update the container or change something in the template. You can trigger it by just erasing a character and entering it again in any of the fields and then hit apply.

If it's trying to get a new cert, you have not managed to use the same appdata folder as you did for letsencrypt.

It's still not correct even though you followed a guide. You do not own duckdns.org. you "own" blahblahblah.duckdns.org, so add that to domain name. Subdomains will be subdomain.blahblahblah.duckdns.org.

You can use the same container for both. Just create a new database for each instance that need it.

Your URL is not duckdns.org, it's your_user.duckdns.org. You don't own duckdns.org.

Post the docker run command. Screenshots doesn't tell us everything.

Looks like you should check your disk for errors.

Post the screenshot so we can see that your port forwards are correct and also the other info missing.

The IP in the screenshot is the LAN adress. You have to find the WAN adress and compare it to the one provided by the webpage. If those two are not the same, then you are behind CGNAT. Hard to say if your port forward is correct as we don't see the description of the port forward table and we also don't have the docker run command of swag to see the validation method you have set up. It looks like you have not port forwarded to 80 to 180, but to 80.

No it will not be an all in one.

That is not something we have even considered and will probably not happen. We do have the LTS tag.

I never tried it, so how can you add photos in the container? If it's a path, then add your photo share as a new path to the container and use the container path you set in Digikam.

It's just a fancy bookmark tool, so don't think you would be able to launch a VM. You might be able to connect to it if it'susing VNC that you can use in a browser.

Not until Alpine linux releases 3.13 and we rebase to the new version.

Please post the docker run command.

What is with the attitude? I asked about a pretty simple question which you should be able to answer if you remember how you set up nextloud. When settin up nextloud you choose a database and you need to check if that is running if it's an external one. If you chose sqlite, it's in nextloud and it might be corrupt. All we know is that you scream, like a child, that your nextcloud doesn't work and doesn't supply any info that were asked for. Not much we can do to help then.