HTTPS localhost error message when logging is selected

Solved1.42K viewsHTTPS localhost
2
0 Comments

A customer recently changed from HTTP to HTTPS which is mostly working, but if the logging is selected an error message appears.

Dominik Kosteletzky [DevOps Advocate] Selected answer as best 11th March 2022

2 Answers

2
6.59K 1 Comment
  • Has the FQDN been configured in the maintenancesettings.xml (see help)?
  • To open Cube, instead of using http://localhost, also use https://fqdn/. See the help on how to configure an auto redirect to https.
Jeroen Geldhof [SLC] [DevOps Enabler] Posted new comment 11th March 2022
Jeroen Geldhof [SLC] [DevOps Enabler] commented

the MaintenanceSettings.xml was changed regarding the guide, but it still does not work.
3
2.71K 1 Comment

Hi Dominik,

Is there an HTTP to HTTPS redirect configured on your web server (IIS)? If so, this error may be fixed by skipping the redirect on “localhost”.
I also wonder if you get the same error when you use the FQDN (or hostname) to open Cube?

Jeroen Geldhof [SLC] [DevOps Enabler] Posted new comment 28th March 2022
Jeroen Geldhof [SLC] [DevOps Enabler] commented

URL Redirect from http to https is active (with skipping for Localhost) is active, but same error happens when redirect rule is inactive.
Error 403 (when trying to access logs) happens when using Cube with FQDN (doesn’t matter if local on dma or from a client).
When using Cube inside IE with http and localhost, we got the message shown in the screenshot here:
https://community.dataminer.services/question/https-localhost-error-message-when-logging-is-selected/
Using Cube inside IE with FQDN and https is however not possible. IE starting loop on my Win10 Client and
“An Error occured in the application you were using” from DMA with FQDN and my Win 7 CLient.

Update:
Access to Cube inside IE is possile again when adding fqdn to trusted sites.
But logs are still not accessable (Error 403).