Cyberes

``` RuntimeError: This version of jaxlib was built using AVX instructions, which your CPU and/or operating system do not support. You may be able work around this issue by building...

You should contact Paperspace and report your issue. AVX exists in all modern CPUs so something is broken on their end.

Actually, I had an internal lighthouse that only the hosts on the same network as the `rsyslog daemon` host could. I removed that and things seem to work now. Thoughts?

Sorry, not surprised my confusion carried over to you. Let me try and explain... When I first created this bug report, I believed that having multiple IPs listed for one...

Okay, let's keep breaking this down. Logs are coming (I have to re-create the setup I had when things weren't communicating). > What is the inaccessible Lighthouse's Nebula IP? It...

Sorry, things got busy with school starting back up. I think I have time to do some more debugging. I'll have those logs somewhat soon.

Okay, I checked the status of the rsyslog server and it does not seem to have a Nebula connection. I can't ping its address and I can't ping any other...

Just want to clarify that my rsyslog server has dozens of connections to my other servers.

The earliest log entry I have is this: ``` Oct 16 01:43:15 syslog nebula[149]: time="2023-10-16T01:43:15-06:00" level=info msg="Handshake message sent" cached=true handshake="map[stage:2 style:ix_psk0]" relay=172.0.0.2 vpnIp=172.0.4.8 Oct 16 01:43:15 syslog nebula[149]: time="2023-10-16T01:43:15-06:00"...

I mean that I set the config back to how it was when I originally encountered the issue so that I can collect the logs.