Hard coded request for HTTP in Designer Launcher even if gateway set up for HTTPS

Ignition Early Access
8

Thanks @Kevin.Herron and @accyroy. I was able to confirm the same as you had that a request towards /main/StatusPing was the culprit. I’ve got the same setup in Traefik and was able to mitigate it using the same strategy by applying my container labels (running with Docker) like such:

labels:
  ...
  - "traefik.http.middlewares.ignition-replacepathmain.replacepathregex.regex=^/main/StatusPing$$"
  - "traefik.http.middlewares.ignition-replacepathmain.replacepathregex.replacement=/StatusPing"
  - "traefik.http.routers.ignition.middlewares=ignition-replacepathmain"

Having the reverse proxy perform the substitution instead of the gateway seems to do the trick, just like described above. Thank you both once again!

4 Likes