Redirection to wrong port with Traefik reverse proxy

[Pingumania]

For example when I add or change a watch, I get redirected to port 444 instead of 443.
Port 444 isnt a random port, is has to do with my setup, but since this only occurs with changedetection.io so far I figured I open this issue here. This could also be an traefik issue or even by design.

Version
v0.39.7

To Reproduce
Steps to reproduce the behavior:

1. Go to change.mydomain.xyz
2. Click on 'edit' on a watch
3. Click on 'save'
4. Get redirected to change.mydomain.xyz:444

Expected behavior
Get redirected to change.mydomain.xyz:443

Desktop (please complete the following information):

• OS: Windows 10
• Browser Firefox 96.0.3

Additional context
I have multiple entrypoints in traefik and one listens on port 444. Here is the config:
docker-compose.yml

  traefik:
    image: traefik:latest
    container_name: traefik
    restart: always
    networks:
      - proxy
    ports:
      - public_ip:443:443/tcp
      - public_ip:80:80/tcp
      - vpn_ip:80:81/tcp
      - vpn_ip:443:444/tcp
    environment:
      - CF_API_EMAIL=${CLOUDFLARE_EMAIL}
      - CF_API_KEY=${CLOUDFLARE_API_KEY}
      - TZ=${TZ}
    volumes:
      - ${DOCKERDIR}/traefik/acme.json:/acme.json:rw
      - ${DOCKERDIR}/traefik/dynamic:/dynamic:ro
      - ${DOCKERDIR}/traefik/traefik.yaml:/traefik.yaml:ro
      - ${DOCKERDIR}/traefik/logs:/var/log/traefik:rw
    labels:
      - traefik.enable=true
      - traefik.http.routers.traefik.entrypoints=vpn-secure
      - traefik.http.routers.traefik.rule=Host(`traefik-vps.${DOMAINNAME}`)
      - traefik.http.routers.traefik.tls.certresolver=letsencrypt
      - traefik.http.routers.traefik.tls.domains[0].main=${DOMAINNAME}
      - traefik.http.routers.traefik.tls.domains[0].sans=*.${DOMAINNAME}
      - traefik.http.routers.traefik.service=api@internal

  changedetection:
    image: ghcr.io/dgtlmoon/changedetection.io
    container_name: changedetection
    volumes:
      - ${DOCKERDIR}/changedetection:/datastore
    restart: unless-stopped
    networks:
      - proxy
    environment:
      - PORT=5000
      - PUID=${PUID}
      - PGID=${PGID}
      - BASE_URL=https://change.${DOMAINNAME}
      - WEBDRIVER_URL=http://chrome:4444/wd/hub
    labels:
      - traefik.enable=true
      - traefik.http.routers.change.entrypoints=vpn-secure
      - traefik.http.routers.change.rule=Host(`change.${DOMAINNAME}`)
      - traefik.http.services.change.loadbalancer.server.port=5000
  
  chrome:
    container_name: chrome
    image: selenium/standalone-chrome-debug
    networks:
      - proxy
    volumes:
      - /dev/shm:/dev/shm
    restart: unless-stopped

traefik.yml

entryPoints:
  web:
    address: ':80'
    http:
      redirections:
        entryPoint:
          to: web-secure
          scheme: https
  web-secure:
    address: ':443'
    http:
      tls:
        certResolver: letsencrypt
  vpn:
    address: ':81'
    http:
      redirections:
        entryPoint:
          to: vpn-secure
          scheme: https
  vpn-secure:
    address: ':444'
    http:
      tls:
        certResolver: letsencrypt

[dgtlmoon]

- BASE_URL=https://change.${DOMAINNAME}:444 ?

[Pingumania]

Same behaviour

[Pingumania]

This is the log entry from traefik:

2022/02/01 21:23:10 transport.go:2242: Unsolicited response received on idle HTTP channel starting with "0\r\n\r\n"; err=<nil>

[dgtlmoon]

sounds like an issue with traefik, if you would like commercial support, please email [email protected]

[dgtlmoon]

 HTTP channel starting with "0\r\n\r\n";

\r\n is windows style return line feed stuff too..

[Pingumania]

I looked around abit and found these related issues/topics:
caddyserver/caddy#4445 (comment)
traefik/traefik#3295
golang/go#19895

Seems to be an error message generated by Go, both traefik and caddy use it.
This error message might not even be related to my issue, it just appears at the same time.
This isnt a high priority issue for me, once I have set up everything it shouldnt bother me.

What I will try is to use the entrypoint with port 443 and see if the error disappears.

[Pingumania]

The error message is still there but the redirect issue is gone with entrypoint on port 443.