“Pre-install Bacularis command” error on IPv6-only client

michaeldolzani

I’m trying to add a client via the Deployment section, but during the Pre-install Bacularis command step I get the following error:

===== Step: Pre-install Bacularis command ===== ... Err:5 https://packages.bacularis.app/stable/debian bookworm Release Cannot initiate the connection to packages.bacularis.app:443 (3.120.118.12). - connect (101: Network is unreachable) ... E: The repository 'https://packages.bacularis.app/stable/debian bookworm Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. EXITCODE=100 quit

The issue seems to be that the client machine now uses IPv6 only and no longer has IPv4 connectivity, while the installation process is attempting to connect to the host via IPv4.

Is there a way to force the client or the deployment command to use IPv6 when connecting to the Bacularis repositories? Or is there a recommended configuration for IPv6-only machines?

Thanks!

gani

Hello @michaeldolzani,

This is interesting question. I don't know this topic well but I guess your assumption for connection problem from IPv6-only to packages.bacularis.app host can be correct. I have to admit that for now we are not ready to add IPv6 support on the server side (we need some time and resources for that).

Probably on your client side there is possible to add some form of translating IPv6 -> IPv4. On the Internet I have seen easy one-line examples with using socat tool to do a local proxy but I have not tried them. This could be done for the Bacularis deployment time only.

If you find a way to do it on the client side, it could be kind of you to describe it here on the Bacularis User Group in this thread. This way all other Community users with this type of setting could use it easily as well. We could also add it to the documentation to the Troubleshooting section.

Thanks in advance for your help.

If any other Community users experienced this problem and solved it, please let us know here and share your solutions. Any kind of help is appreciated.

Thanks.

Best regards,
Marcin Haba (gani)

michaeldolzani

Hi @gani ,

thank you for your reply.

I wanted to share how I solved the issue.

In my case, I configured the server so that its default gateway points to a dedicated internal interface. Then, on the upstream Hetzner gateway, I added a static route so that the default 0.0.0.0/0 is routed through the firewall interface. After that, the server started accessing the Internet correctly through the firewall.

On the firewall, I simply allowed outbound traffic on port 443 for the two internal networks involved. With this setup, everything now works smoothly, including access to packages.bacularis.app.

I hope this information can be useful for other users with a similar configuration.

Best regards

gani

Hi @michaeldolzani,

Thank you, @michaeldolzani ! 🙂 That's fantastic that you provided this solution 👍️ This will be helpful for other Community users with similar environment.

Best regards,
Marcin Haba (gani)