Error 100

Hello @Eugene

Welcome to the Bacularis user group.

Could you tell us if during installation tests in the installation wizard steps (test buttons) finished successfully?

I would advise to enable debug in Bacularis (click the gearwheel icon at the top left side and then please check the Enable debug checkbox). After enabling the debug, please refresh the page.

I don't know what installation method you used, so I provide the relative path to the debug log:

[main Bacularis directory]/protected/Web/Logs/bacularis-web.log

Are you seeing any error there? If not, then please check if there is any error in the web server error logs.

Thanks.

Best regards,
Marcin Haba (gani)

I am having this problem too, however, I had a working installation and tried to change from HTTP to HTTPS and get the error. I've looked over the configuration and it appears to be correct. After getting the error I tried to revert to just using HTTP and I still get the error. All I can find is that this is due to having the configuration set incorrectly, but I've gone through the config files and the configurations in Bacularis and it appears to be correct. I can still log into UI with either setting when I change back and forth between HTTP and HTTPS, but I always get the splash screen indicating an error 100 with the message: Problem with connection to remote host. cURL error 0: .

Hello @Gerard,

Welcome to the Bacularis user group.

If you change the HTTP => HTTPS connection manually in the Bacularis web server config, then you need to switch the connection between Web => API to HTTPS as well on the web interface. Here you can read how to do it:

https://bacularis.app/doc/brief/troubleshooting.html#error-100-after-switching-connection-from-http-to-https

For users changing the HTTP => HTTPS connection with installing the certificate in Bacularis web interface function, this switching Web => API communication to HTTPS is done automatically for the default Main API host. I mean these certificate installation methods:

https://bacularis.app/doc/brief/installation.html#enable-ssl

Best regards,
Marcin Haba (gani)

gani I have checked and both the hosts.conf file and the web interface are set to use HTTPS. In the application settings however, my UI does not have a tab for SSL certs. I am running a version of Bacularis that was installed using the RPM repository for Rocky Linux 9. Version 4.0.0 is what the documentation on the Bacularis web site shows. I have had to add the SSL certificate and key information into the HTTPD config file for bacularis.conf in order for me to connect to the UI with HTTPS, but nothing shows anymore, and I just get the splash screen with the error.

I did try backing out the changes, but the splash screen still occurs and I cannot find any obvious error in any of the log files.

gani the results from enabling the debug didn't cause a bacularis-web.log file to be created. The only log file in the location that I found was bacularis-audit.log file. The audit log file just shows me successfully logging in.

The results from the second test using the test button on the edit page for the API Hosts are just the message I get in the splash screen, except in triplicate:

Problem with connection to remote host. cURL error 0: .
Problem with connection to remote host. cURL error 0: .
Problem with connection to remote host. cURL error 0: .

Actually, I was able to find the bacularis-web.log file in a different location. This log file does has a repeating error in it with just different timestamps:

2025-03-21 16:36:01 [Application] BaculumAPIClient.php:189: API REQUEST ==> https://[hostname]:9097/api/v3/config?director=

2025-03-21 16:36:01 [Application] BaculumAPIClient.php:460:

2025-03-21 16:36:01 [Application] BaculumAPIClient.php:486: stdClass Object
(
[error] => 100
[output] => Problem with connection to remote host. cURL error 0: .

Hello @Gerard,

Thanks for checking the debug and for providing more details.

In this case could you use in your web browser address bar this address (with hostname replaced to your real Bacularis hostname):

https://[hostname]:9097/api/v3/config?director=

You will be asked about providing API username and password in the HTTP basic auth window. In most cases, if you did not change it, it will be the same username and password as your Bacularis web administrator login and password.

Are you seeing any error now? If not, then I would propose to enable debug on the Bacularis API side as well. To do it, please log in to the API panel and enable debug in the API Panel path:

[Main menu] => [Page: Settings] => [Tab: General] => [Checkbox: Debug]

At the end please try this address in the web browser address bar once again

https://[hostname]:9097/api/v3/config?director=

Best regards,
Marcin Haba (gani)

gani I was able to resolve the issue by using DNF to remove the package installed by the repository, and installing version 4.8.0. It took some time to do, but I have it working again and am at the latest version that was available to download. Thanks for your help!