SCIONLab problem

[minichesco]

Hello, my name is David. I am a student currently working on my final thesis about the SCION network architecture. I decided to take this path because my advisor suggested it to me, and I found it very interesting.
To work with SCION technology, I saw the option to use SCIONLab. My goal is to run the SCIONLab topology locally on my own machine using a VM and observe its behavior through the SCIONApps and the visual web tool.
Before explaining my issues, I want to highlight that I have NOT filled out the form to become a node in the SCION infrastructure at any point, so I don't know if my issues could be solved through that process.
Moving on, I have followed all the steps from the SCIONLab tutorial website — from creating my own AS, downloading and setting up the VM, installing Vagrant, and running the Vagrantfile to deploy my AS configuration, all the way to the troubleshooting guide. However, after completing all the steps, I have consistently encountered some issues that I will now describe.
My AS is attached to 17-ffaa:0:1113 (ETH-Hell-AP), configured with VPN and using port number 50000. I should mention that I have not modified the Vagrantfile at all — it is the default version downloaded from the SCIONLab website.
To check the network functionality, I first started all the services and verified they were active. Then I tried to ping the next node in the topology (17-ffaa:0:1112), but I got the error:
Error: fetching paths: no path available
To identify the cause of the error, I checked the border router, the VPN tunnel, and the beacons.
First, I verified the VPN tunnel using:
sudo systemctl status openvpn@client-scionlab-*

It showed as active, but gave a warning that I took note of.

Next, I checked the border router using:
sudo journalctl -u scion-border-router@br-1.service

And I received the following error (I’m sharing the error directly instead of a full log since it’s too long):
scionlab-ffaa-1-11fb scion-border-router[9537]: }}: Error setting up connection {listen=10.5.0.139:50000; network=udp4; remote=10.5.0.1:50095}
scionlab-ffaa-1-11fb systemd[1]: scion-border-router@br-1.service: Main process exited, code=exited, status=1/FAILURE
scionlab-ffaa-1-11fb systemd[1]: scion-border-router@br-1.service: Failed with result 'exit-code'.

Finally, I checked the beacons, although since the border router wasn’t running, I expected it wouldn’t work. For that, I ran:
sudo journalctl -u scion-control-service@cs-1.service

And received the following error:
scionlab-ffaa-1-11fb scion-control-service[9534]: 2025/08/18 10:08:53 connection doesn't allow setting of receive buffer size. Not a *net.UDPConn?. See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details.

To see if there were any additional problems, I launched the SCION visual web tool and used the built-in Health Check feature.

There, I confirmed that indeed there were no paths available, and the tests for both the border router and beacons failed. Additionally, it indicated that a directory did not exist and advised me to contact the developers.
At this point, I need help to resolve these errors and continue my project, as I believe SCION is a great architecture and it’s very exciting to work with it, even in a controlled virtual environment.