saarg

I don't think aptalca have not made any containers in his private repo since he joined linuxserver a long time ago. I don't know the app, but seeing it is a photo management software, I don't see a reason why it would need host networking. So bridge mapping port 3000 should be good. As for folders, you can add your own mappings as you see fit. I like that approach better. You will have to check the proxy conf repo or the proxy-conf folder of swag for a RP conf.

Why not use the proxy conf included in swag?

Have you tried turning off auto play next episode?

Yes I know what the issue is, but not the solution.

Not sure what your issue is, as I don't see it here. Not sure what is in my cpnfigs, but on mobile arm so can't check until later today.

Looks fine here

You are not using unraid, so this is not the correct place to post this. There should not be any need to chown the volume. Then you have something wrong in your setup. Join our discord if you want to figure it out.

You updated them or deleted them and let the container recreate them on restart? Which files in which container did you update?

Do you have issues with the disk or file system errors?

You might have very old config files, so I would recommend you to check the date at the top of the config files in both swag and nextcloud and compare them with the ones on GitHub. The files I can remember is the default, proxy.conf and nginx.conf

Is this inside your network or using cellular data?

You can just use the booksonic template and change the name and repository to booksonic-air.

Have you tried a different browser or private mode?

That isn't detailed. I don't know the guides you have followed, so of you want help, you need to post what you have done.

You have to post exactly what you have done.

I'm not quite sure what you want to achieve here, but you will never be able to run without ports. Somewhere you have to define the port. You can remove the need to specify a port in the container template by running the containers in a custom network and take advantage of the DNS in the docker network. Doing this you have to have swag (which needs ports defined) and all container in the same custom network. But you still have to define the ports in the proxy configs. You can also take advantage of swag running your webserver, as it is a webserver.

If you can't connect to the webserver at the port you have mapped in the container template, your webserver is not running. It might also be a good idea to post the docker run command so we can see if you have mapped the port correctly.

If you would have read the readme on GitHub, you would have found this information in the application setup part 😉

Pfsense in an in a 1u supermicro rack server with an 8-core Xeon, 32GB ram and an SSD. Just a little bit overkill. Will probably install proxmox or something similar at one point to be able to test other firewalls.

All routers work with swag as long as it support port forwarding. If you want to use the domain inside the home network the router should support hairpin NAT/split DNS. Both ubiquiti and pfsense works.

It's most likely spun down drives or something like that. There was someone mentioning optimizing the database settings to speed things up in this thread, if I remember correctly.

There was no anger or tone meant from my side. I was just pointing out that it doesn't have anything to do with our mariadb since the nginx proxy manager have its own MySQL server running inside the container.

It still doesn't have anything to do with our container. There is MySQL inside the container. It's pretty obvious from looking at the screenshot you posted. Starting mysqld /usr/bin/mysqld

I'm not sure what nginx-proxy-manager has to do with our mariadb container? The above screenshot doesn't look like it's from our container.

I can't say as I don't really know what happened. I can however say that I'm on 18.0.6 and have updated to the latest container and have no issues, so there might have been something else causing the issue.