aptalca

This needs to return an ip address: https://dnschecker.org/#A/sonarr.s2white.com See here for details setup info: https://docs.linuxserver.io/general/swag

Yup

Sounds like we all have the same first name 😅 The only potential issue I'm aware of is in nextcloud's config.php where you allow a proxy. You'd have to change that to swag if you change the container name (and if you reverse proxy nextcloud)

Code-server already has that functionality built in where it can proxy a service on a port via the port as a sub-subdomain. Look into the proxy_domain env var

Please take this discussion to the appropriate thread. This is the openvpn-as thread. Thanks.

Put in the full url including http:// in app settings

Pfsense on an embedded celeron mobo with 4gb ram, an intel dual gigabit nic (pci-e), cheapest, smallest ssd in the cheapest case with a built in psu.

Those are all some good options, but just a reminder, the name of the app is an acronym so it should be all caps

Put it in the main server block in the default site conf located at "/config/nginx/site-confs/default". That will take care of the main domain and all subfolder proxies.

This container should detect all gpus active on the host system whether they're accessible by the container or not because it queries (iirc) the kernel modules/drivers. If the Nvidia card is available on the host (driver loaded), it should be detected and listed here even without the gpu uuid passed. But without the uuid passed, it won't be able to access it. If you're not seeing the card listed, it suggests the driver is not loaded on host. Perhaps it is stubbed, or passed through to a VM.

In your previous question, you were asking about subfolder. They are handled differently. The basics are that, server blocks are parents of location blocks. If you put the deny in a server block for ombi, it will work for that subdomains and all child location blocks. A subfolder proxy conf is a child location block of the main domain's server block. So to answer your last question, if you add the allow/deny into ombi subdomain's server block, it will only affect that subdomain, not the main domain as the main domain is served under a different server block.

Could be browser cache. Try an incognito window

If you give pihole its own ip, it will use macvlan network type. That type blocks connections between the container and the host (and everything else bridged on host) as a security feature. So swag won't be able to connect to pihole. We highly recommend running pihole on bare metal (an rpi gets the job done) instead of in docker. The subfolder confs get included in the main server block in the default site conf. You can edit that.

Likely your api key is not correctly added or is not correct If you're getting the default landing page, then likely the proxy conf is not activated correctly. Check its name, and check the server name directive

Yeah, the time for a release to go from beta to stable is pretty short. I guess they're more like release candidates but that could change and it's all up to plex.

That's really a question for plex. With that said, I've personally been on the beta/plexpass track for years and never had any issues.

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

There is no stable 1.20 yet. When there is, our builder will push out a new image with it. You can set the version to docker and it will use the version the image comes with.

You need to use the host IP and the host mapped port in the proxy conf for it, instead of the container name and and container port

That's the latest stable release. If you want betas, the instructions are in the readme.

There is already an image tag called "v4-preview" for testing and dev purposes. When tidusjar (ombi dev) pushes v4 to master/stable, our image will update the latest tag accordingly.

I mean, the EOL for python2 was announced 12 years ago. It's not like it crept up all of a sudden. 😁

Python2 is EOL and is therefore removed. It's in the changelog

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

I don't follow. What's "HTTP blank"? You'll have to be provide a clearer description of the issues you're having.