Could not reach the /healthcheck/status after upgrade to 4.12.1

[crushian]

Checklist
I have read intro post: https://community.passbolt.com/t/about-the-installation-issues-category/12
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
I describe the steps I have taken to trouble shoot the problem
I describe the steps on how to reproduce the issue

I am running a source installation on Ubuntu with Apache as my webserver. The healthcheck was passing w/o issue on 4.10.1. After checking out 4.12.1, the “Could not reach the /healthcheck/status with the url specified in App.fullBaseUrl” erorr started occuring. I followed the documented upgrade proceedure for source installations as I have done many times in the past w/o issue.

My passbolt instance is hosted in a subdirectory so my configuration uses the ‘base’ setting for the ‘App’ so that I have something similar to:

‘App’ => [ ‘fullBaseUrl’ => ‘https://my.site.net’, ‘base’ => ‘/passbolt’ ]

Accessing https://my.site.net/passbolt/healthcheck/status.json gives:

{“header”:{“id”:“c98c868d-4945-4dd7-b210-f94a42c0ae79”,“status”:“success”,“servertime”:1743772918,“action”:“f52ecf6c-8e82-5f3d-ab73-f6df46eb71b5”,“message”:“OK”,“url”:“/passbolt/healthcheck/status.json”,“code”:200},“body”:“OK”}

Otherwise, the application appears to be working fine, except the healthcheck script is also reporting my certificates are self-signed and don’t match the hostname which is nonsense. I know they’re fine and my browsers think they’re fine, so healthcheck is the only outlier here.

Thanks for any help.

[crushian]

Nevermind. I had a DNS configuration issue. Sorry for the noise.

[gyaresu]

Mate, “it’s always DNS”. We’ve all been there