Beagle Bone AI-64 ssh working, but browser connection refused

Hi all,

I am relatively new to the processor world so please forgive any naivity :slight_smile:

I just got a Beagle Bone AI-64 and am trying to connect to it through my browser. I have a new Macbook Pro (M1) and am connecting through USB-C. I flashed the most recent Debian to a microSD card and have the BB booting off this. I also have the BB powered through a barrel connector to a DC power supply at 5V (Seems the Mac USB ports can only output up to 500mA so this won’t cut it for power). I find the network adapter does show up with IP assigned to my computer, and for the BB. I can actually even SSH into debian@ just fine.

The issue is that I can’t seem to navigate to the BB through my browser. I first encountered a “403 forbidden” error when trying to browse to the BB IP. I was able to get around this at least through the advice of this forum post:
which suggests to use port 3000 instead of 80. I assume this meant on the BB itself? I was able to ssh and change the port.conf file on the BB like so
sudo vim /etc/nginx/sites-available/default
And changing the server port from 80 to 3000.
Now I no longer get the Forbidden 403, but I do still run into an issue with either Chrome or Firefox where it says “ refused connection”. Any thoughts on why this is happening if I am able to ssh no problem? I have been toiling away with the Chrome and Firefox settings to see if there is some issue with security, but even on the “no security” modes, I get the same result. Thank you in advance for any advice!

Best Regards,

$ ssh debian@

“Forbidden 403” is nginx blocking access, I fixed this after release, so your using an old image.

The fix is to add: autoindex on to location in:

sudo apt update
sudo apt install --only-upgrade bb-customizations
sudo cp -v /etc/ /etc/nginx/sites-enabled/default
sudo systemctl restart nginx.service

Port 3000 is VSCode, so by switching nginx from 80 to 3000, you now have two different service files fighting for port 3000, thus breaking both…

You can always grab the latest image to fix your changes: