Change 443 port

Configuration
1

Hello all,

I’m wondreing if it’s possible to use another port than 443.

My 443 port is used by another application.

Thanks

2

You haven’t provided any info about your setup so???
HA uses 8123 are you forwarding 443 to 8123?

You could/should use a reverse proxy like Caddy and that will solve the issue (whatever it is)

3

I had 2 rules : 443 to 8123 and 8123 to 8123 it worked fine until i changed the router today.

In the new router, i can’t use 443. and All google home i have don’t work.

I use DuckDNS and lets’encrypt to access to my setup on HTTPS

Thank

4

You should use a reverse proxy.
You can try a different port say 40443 to 8123 and then append :40443 to the URL in Google etc.

5

I think there is a problme with my Duckdns

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
# INFO: Using main config file /data/workdir/config
ERROR: Problem connecting to server (get for https://acme-v02.api.letsencrypt.org/directory; curl returned with 6)
EXPECTED value GOT EOF
[cmd] /run.sh exited 1
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
6

Sounds like the issue is just a missing port.
The S in HTTPS means secure and where HTTP normally run on port 80, then HTTPS is usually run on 443.
If you to not set a port in you URL, then port 443 is assumed as default, but you can just set a port with “:”, like https://www.somedomain.com:8123

7

You will need port 80 to 80 for Lets Encrypt to get a certificate. If you use Caddy you can use the DNS challenge.

8

Lets Encrypt just need port 80 on the external side of the NAT/firewall.
Internally you can have what port you like.

9

With the old Haaska setup from Github it’s possible to get it working without forwarding port 443. But the instructions are verry outdated and therefore tricky.