Setup a DNS Name on my firewall and I can't login / SSL Cert

[wt9bind]

Hello,

I have pulse running at internal IP 192.168.1.101:7655 and I can login no problem to Pulse.

I have setup a dns entry of pulse.mydomain.com on my firewall.
If I hit http://pulse.mydomain.com:7655 the first thing I notice is that the login screen is not in dark mode like the IP site is. Secondly, I cannot login with my credentials when I go to the DNS site

My second query is about applying an SSL certificate to pulse. Is there a step by step guide on using something such as certbot to do this, please?

I must say that I am a noob, so I am sure this is an easy solution (please go gentle on me).

Thanks in advance.

[rcourtman]

The different theme (dark vs light) between IP and DNS access suggests the browser is treating these as separate origins. Your login session and preferences are stored per-origin, so they won't transfer.

A few things to check:

1. Session issue: Try logging in fresh via the DNS URL. The IP login won't carry over to the DNS hostname since they're different origins from the browser's perspective.

2. Make sure you're using the same port: Confirm http://pulse.mydomain.com:7655 (with port) is correct.

3. Firewall/DNS routing: Verify the DNS name actually routes to the same machine as the IP. You can test with curl -v http://pulse.mydomain.com:7655 to see what happens.

Regarding SSL: Pulse itself doesn't handle TLS termination. The common approach is to use a reverse proxy (Caddy, nginx, Traefik) that handles SSL and proxies to Pulse on the local port. Caddy is probably the easiest since it auto-provisions Let's Encrypt certificates.

Basic Caddy config:

pulse.mydomain.com {
    reverse_proxy localhost:7655
}

That would give you HTTPS with auto-renewed certificates.

[wt9bind]

Thank you for replying. It was my browser. I cleared cache and it resolved.

I also setup Caddy and it works great. I do see that Pulse does say that it says that HTTPS is still off under overview though.