Boa tarde,
Alguem poderia me ajudar. Habilitei o force htpps e agora não conseguido acessar mais a pagina de administração.
Hi and welcome to our Community!
Do take a look at the solution provided in this post:
When FORCE HTTPS ON is selected in the CMS, on every request we have the PHP code check that the HTTP_SCHEME is in HTTP_X_FORWARDED_PROTO is https and if it is not, we issue a redirect to https.
What is happening for you @aponkye is that your https:// URL does not contain https because the proxy is not setting that correctly.
You could put a really simple test file in /custom/userscripts called test.php containing:
<?php
echo 'Testing HTTPS' . PHP_EOL;
echo 'REMOTE_ADDR: ' . $_SERVER['REMOTE_…
Do let us know if this solves your issue
Tem alguma outra forma de ajustar essa configuração, queria desmarcar essa opção de forçar pelo https.
Olá Natasha. Boa tarde!
Você consegue indicar alguém para prestar uma consultoria para me ajudar no meu problema sobre habilitar o https e ficar sem acesso a pagina de administração?
The only way to turn that setting back off is via a database edit as mentioned here:
This setting:
[image]
Xibo looks at each incoming connection and if it detects that it is using http it redirects to https. If https was working before you enabled it, then you should be fine.
Solution 1 is to make HTTPS work
Solution 2 is to get a command line to the database and set the setting back again.
UPDATE `setting` SET value = 0 WHERE setting = 'FORCE_HTTPS';
Thanks,
Dan
If this is with Docker, then to run the command you would need to do the following:
While troubleshooting an issue you maybe asked to run a SQL statement on your database Docker container, or you may want to run a statement yourself for another purpose. To do either of these things there are two options.
Using the command line
Using the GUI called PhpMyAdmin
Command Line
Before you can run a statement inside the docker container you will need to find the container name. This can be done using the docker ps command.
The resulting output will show a list of running docker con…
To fix the underlying issue, assuming the CMS is behind an Apache reverse proxy, you would need to add the following to the Apache configuration:
proxy_set_header X-Forwarded-Proto $scheme;