I’m not surprised that using the IP would give you a certificate name mismatch,
that would be expected behaviour for any website.
I did try changing the https to http and as expected the result is the same (if
there’s a server redirect setup to ssl then httt == https for all requests)
Neil Ba
Interesting. I typed the IP that gave the 404 into my browser, and it came
up with an invalid certificate. It's registered with lets encrypt. chrome
says the cert's common name isn't valid. I bet our browser sessions are
getting a different server than the server your bacula instance is running
on.
I can’t seem to access the Community binaries to update my now out of date
ubuntu bacula install.
Here’s what I’ve done:
Registered for community access
Received mail with access-keys
Downloaded and added gpg key files using
wget
https://www.bacula.org/downloads/Bacula-4096-Distribution-Ver
