Hi JeremyM, thanks for posting this on the community.
I’ve been discussing this with my colleagues and the issue could in fact be related to a misconfigured reverse proxy. If your CMS is indeed behind a reverse proxy it needs a header to be added to each request by the proxy so it knows if the request was made over http or https. If it’s missing, it will assume it was made over http, and so any URLs it sends out will start http.
X-Forwarded-Proto: https
X-Forwarded-For: <IP where the connection comes from> You may find this is is added automatically, depending on the server you are using.
It should be setting those to headers on each request that goes from the reverse proxy to the CMS. The first one should only be on https connections. On a http connection it should set it to http or removed from the request if it’s present. What it mustn’t do is pass that header through from the client - it should always clear it and set it or clear it in both cases.
If you are using an Apache reverse proxy, you can see in this guide how those headers are being set:
Specifically:
I hope this helps to resolve your issue.
Many Thanks.