[bug] Kobo Sync - Generated API using FQDN yields "HTTP" vs "HTTPS" endpoints + Message box is also misaligned on caliBlur! Dark Theme

[jadehawk]

Describe the bug
Kobo Sync - Generated API using CWA hosted on an FQDN yields "HTTP" vs "HTTPS" endpoints:
We get this:
api_endpoint=http://xxxxx.xxx/12345
instead of:
api_endpoint=https://xxxxx.xxx/12345

And the same message box that displays this API/Token is not aligned correctly and looks out of place when using the caliBlur! Dark Theme.
Message box looks perfect in the standard Theme. Tested on Latest Chrome/Brave/Edge Browsers.

Manually changing the HTTP to HTTPS on the api_endpoint=http is all that is needed and Kobo Sync works without an issues.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'PROFILE'
2. Click on 'Create Kobo Token'
3. See error

Expected behavior
Nice and Aligned message box containing the correct api_endpoint. When hosting CWA on a FQDN (TLS) and using the nice caliBlur! Dark Theme.

Screenshots

Configuration(please complete the following information):

• OS: [Debian 12, Proxmox 8]
• Hardware: [x86 server]

[demitrix]

Dug into this a bit, looks like the issue stems from the headers Calibre-Web is using to check scheme. This may be a better fit for an upstream issue. In the mean time, if you configure your reverse proxy to send https in the X-Scheme header then it will be fixed. IMHO this header should be changed out for HTTP_X_FORWARDED_PROTO which is more common. Tested this here and it solved the issue. We'll let @crocodilestick weigh in on this.