Can't Remove Port on Target

[Eric_F]

I think it works! But I notice I can’t access thre traefik dashboard. And in Wappler the password field gets wiped when I deploy

not sure if that’s normal.

Also on deploy I saw

time=“2023-02-18T14:26:53-06:00” level=warning msg=“network proxy: network.external.name is deprecated. Please set network.name with external: true”

not sure if that matters either?

[Cheese]

[Eric_F]

Yeah the portainer one works but not traefik

[Cheese]

Follow D.O’s guide to adding the subdomain for traefik.yourdomain.com

How to Add a Subdomain to Your Domain | DigitalOcean Documentation

[Cheese]

@Eric_F

works but not traefik

Not sure why but could try adding it through D.O instead as I mention above.

[Eric_F]

Alright I’ll look into it. Thanks a ton for all your help. I’ve been at it for a while. Seriously thanks!

[Cheese]

Absolute pleasure to help Eriic! Am sure adding the subdomain via D.O will resolve it for you hopefully!

[Cheese]

Should delete this post in the thread now Eric, contains private information of sorts:

If you want to take a look this is the ip
165.*********
Etc.
Etc.

[Eric_F]

I added the sub domain in DO and it didn’t work so I also changed the web url for the traefik dashboard. And all works now!

@George On here

Using Custom Domains and SSL with Let's Encrypt and Traefik

Intro When you deploy your site you want it to be accessible under your own domain name and also secured with certificate, so that you see the lock icon in your browser and the site is accessible with HTTPS In this Wappler update, we are introducing a new way to handle custom domains and automatically generate free SSL certificates to secure them. All that thanks to two new services: Traefik for easy managing your site and services redirection, working together with Let’s Encrypt for issuing…

it says to use a Wildcard but that seemed to be the problem for me. Also noticed this thread about the same thing.

Traefik

Wild card cnames always had worked when I used them before. What was interesting in this behaviour was that it is the first time I used node 14 not that that should make a difference. and the logs showed it didn’t start even going out to the acme server until I had configured everything in wappler. Even after leaving it for an extended period of time. In the end I had configure the the portainer url and the traefik url before I would even get errors. Then until I created unique records it retu…

Not sure if it’s a bug or what but you may want to look into it or edit the documentation.