Re: can't connect to remote client

On 2025-09-04 09:12, Rob Gerber wrote:
> Gary,
>
> You must not use localhost or 127.0.0.x in any bacula configuration 
> file, anywhere. It will not work correctly if you do. You are seeing 
> the results of that mistake in your system now. If bacula does not 
> initially work with a static IP or FQDN, we must troubleshoot why and 
> resolve the issue.
>
> The bacula configuration files you must check are:
> bacula-dir.conf
> bacula-sd.conf
> bacula-fd.conf
>
> You can search your system for these files with:
> sudo find / -type f -name 'bacula-*.conf'
>
> Please run that find command on both your workstation and your server, 
> and reply with the output, indicating which system gave which output.
>
The files are all in /etc/bacula.

It seems to me that if you shouldn't use localhost / 127.0.0.1 in a 
configuration file, the default configuration files shouldn't use it. 
Instead they should use a descriptive meta-value such as <network name 
of the storage device> or <network name of the changer>. This would 
prevent the services from starting until the values are replaced with 
something legitimate. They would also remove the need for multiple 
comments (most of which are NOT currently in the files) about what the 
value should not be.