Styles broken after moving to HTTPS on DigitalOcean

[ayang]

Hi all,

I just wanted to check that a hacky way I used to fix something is safe / the ‘right’ way…

I installed Passbolt on a DigitalOcean droplet a few weeks ago, and today followed steps to upgrade to HTTPS with LetsEncrypt. Upon doing so, however, the styles of our Passbolt site are all broken, because the page is trying to load the Passbolt css which is still being served over HTTP (mixed content).

The workaround I used was to ssh into the DigitalOcean droplet, navigate to passbolt’s folders, and edit config/passbolt.php to change the fullBaseUrl from http -> https.

Is that safe to do? I couldn’t find any other instructions on how to update the base URL.

Thanks!

Checklist
[X] I have read intro post: About the Installation Issues category
[X] I have read the tutorials, help and searched for similar issues
[ ] I provide relevant information about my server (component names and versions, etc.)
[ ] I provide a copy of my logs and healthcheck
[X] I describe the steps I have taken to trouble shoot the problem
[X] I describe the steps on how to reproduce the issue

[remy]

Hello @ayang,

The workaround I used was to ssh into the DigitalOcean droplet, navigate to passbolt’s folders, and edit config/passbolt.php to change the fullBaseUrl from http → https.

Yes that’s safe to do. The only issue is you need to perform an account recovery as the webextension consider this as a new domain name (not just an upgrade).