minor but neat https / http issue

[admin_de2]

Hi dear Cyclosians,

after switching to https we got errors in the browser-console according insecure source for System-logo, ticket-logo, mobile-logo and favicon.
These ressources are loaded via http, regardless if the current setting in configuration contains https or not.

I could fix the first three by changing the link from http:// to // in Content -> Static Content -> 3x times Header-Sections

Could you please fix that in default content with changing http:// to //? (Missing protokoll uses http OR https - always the right one)

What i could not change, is the URL for the FAVICON.

Can you advise if that is possible? Where?
And please can you change that for the next release?

Many, many thanks to you!

Sam

[alexandre]

Hi,

Probably you are using some kind of proxy for the https.
This way for the Cyclos work properly you need to set the correct property on cyclos.properties file:
cyclos.header.remoteAddress =
cyclos.header.protocol =
Also the https url must be filled at the default configuration.

Regards

[youseftarek]

Hi,

Probably you are using some kind of proxy for the https.
This way for the Cyclos work properly you need to set the correct property on cyclos.properties file:
cyclos.header.remoteAddress =
cyclos.header.protocol =
Also the https url must be filled at the default configuration.

Regards

Hello Alexandre, Appreciated your support if there is any screenshots or steps for this solution as i am a little confused about these line's values.

[stanfidu]

I have the same problem. It doesn't work

[tonyadeleke]

Hi,

Probably you are using some kind of proxy for the https.
This way for the Cyclos work properly you need to set the correct property on cyclos.properties file:
cyclos.header.remoteAddress =
cyclos.header.protocol =
Also the https url must be filled at the default configuration.

Regards

Can you please give a little explanation on how to get to the file! I've been searching the forum for hours without success. I know I can use cli on the container by doing:

docker exec -it example-app bash

But I don't know where to go from there. The file is obviously not accessible from the GUI, except I'm missing something.