saarg

If owning your own domain, I would use cloudflare, especially since your domain registrar doesn't have an API. The advantage of using cloudflare is that you have less things to complicate your setup.

It should be like that if you stop swag. And if you use the wan IP, you get the same respons? You have double up for ports in your Heimdall template. Delete the extra set.

The biggest domain registrars usually have an API to update the IP in case you don't have a static IP, so you don't need a static IP even if you buy a domain. And you can always use the free cloudflare DNS. They also have an API to update your IP.

I haven't really used duckdns, so not 100% sure on how it works, but just logged in and saw that you can create 5 (sub)domains on one account. So the subdomain you create there is the URL you add in the domain env variable in swag. There is no way to configure the subdomains there, so I think those are configured if you add them in the swag setup. If I got something wrong, @aptalca will arrest me 😁 If you use DNS validation you can use wildcard for subdomains so the SSL certificate is valid for everything under blablabla.duckdns.org. But the SSL certificate will not be valid for blablabla.duckdns.org. You should set staging to true when testing, as that will allow you to test the configuration without being rate limited. External port is the port on the outside of your router, 80 & 443. I would set up the dyndns on your router if it supports it.

Read the documentation for the app to see if there is an option like that, but I doubt there is one.

Most people are still going to use duckdns even if they buy a domain, unfortunately, as space invader says so...

What exactly did you do from the link I posted and what were the results? You got to the nginx landing page using both http and https? You did add your duckdns token?

Don't use duckdns.org as the domain. You don't own it. you need to use whateveruseryoucreated.duckdns.org as the domain and then the subdomains are subdomains.whateveruseryoucreated.duckdns.org You might also have the port forwarding wrong. You need to forward port 80 also since you are doing http validation. External port is 443 and internal port is 1443. Hard to say what you have in your screenshot as it's in german Also port forward external port 80 to whatever port you have on the swag container.

I would just use duckdns then and not use tplink at all. As I have said before, turn off swag and then see what happens if you go to the wan IP. If it still loads Heimdall, you have a port forwarding issue. If nothing loads, you have configured something in swag that makes Heimdall load. PPTP does not use port 80, so it the problem with Heimdall is not the issue.

You still have to use youruser.duckdns.org in the domain as you do not have control over duckdns.org. Subdomains are subdomain.youruser.duckdns.org. If you only have one subdomain, you don't need that comma after it, but you shouldn't have anything there for now, unless you want subdomains also. It might be that your ISP is blocking port 80. Go through this troubleshooting guide https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/

Sounds correct. Does it work? What I don't understand is the use of duckdns if you have your own domain. If your domain registrar doesn't support any dyndns, you can use cloudflare for free.

You don't own duckdns, do you? You have to set the domain to whatever username you created at duckdns also. Not only duckdns.org.

Probably better to ask plex directly.

You will get that page when you just use the IP as nginx, the webserver doesn't know what you want and serves the default landing page. Don't enable the subfolder again. That is probably what have caused all this. Regarding the subdomains, I didn't mean the server one, but all the others you made. No point if you use subfolder for those apps.

Because you don't understand how volume bind mounts work in docker? Always post the docker run command if you want help.

Why have you created subdomains in the swag container if you use subfolder? You only activate one of the configs, not both.

The lua error have been answered a couple of hundred times already in this thread and is harmless. You get the Heimdall page because you have configured it this way. Bit it's hard to troubleshoot this as you can't say what you have done. I would just start from scratch and set it up again and then note what you are doing while you are following the guide. That way we are able to help.

You might be better off not posting the same issue in multiple threads. It's hard to follow what has been done. You only enable one of the reverse proxy configs depending on if you want to do subdomain or subfolder. There are instructions if you have to do something to do proxy conf or not. You can easily check if this is a port forward error or reverse proxy by stopping one of the two containers and test what happens if you try to access your IP/domain from the outside.

There is nothing wrong in those files that I can see. Doesn't look like you have changed anything. Which address are you using when you get the issue? Try clearing your browser cache. You have hidden the address/IP you used in your first screenshot, but I can see you are using port 1443. If you have a domain you don't use the port after the domain. If you have been using the IP of your server, there is no need to redact it as it's an internal IP.

Calibre is not a webgui. It's running as an app inside the container and you are using guacamole to connect to the "desktop". So adding /mobile will not work. Where did you read that you can add /mobile at the end of the URL?

You need both a redis and a database container.

It's better to copy the text and add it as code in the post. That way it's easier to read and you can redact your mail and URL. The easiest way is to mark the text, copy it and add it as code. You post all the configs that you changed. We can't know which ones you changed.

If you have set up nginx to serve Heimdall as the landing page, then it's no wonder that you get Heimdall when opening the webgui link in swag. Of you want help, the best way is to provide the config files you have changed stuff in. That way it's much easier for the ones helping. The docker run command is the command popping up when you update or change something in the container template. Just add something to a field and remove it, then hit apply and you will get the command.

Did you enable both decode and encode in the plex settings?

Both your database and redis does not resolve. Is the redis and database container in the same custom bridge? If not, then use the IP instead of name.