Closed Gitfoe closed 2 weeks ago
You are using as VPS a RPI3 ? This may be the problem... It's really really slow...
You are using as VPS a RPI3 ? This may be the problem... It's really really slow...
Yes, as a test I was planning to use what I had on hand. I'm aware it isn't that speedy. Perhaps there's some issue with arm architecture compatibility. But following your comment I've rented a cheap OVH x86_64 Debian 12 VPS which seems to have finished the installation just fine. So I will close this issue for now as I've found a workaround. 😊
Expected Behavior
I expect my router to connect to the VPS and communicate via omr-admin and get all its keys and data via the API.
Current Behavior
I set up my home VPS on a Raspberry Pi, forwarded ports 65000-65535 and 443. On the router, after setting up a single unrestricted WAN and entering the Server Key, it didn't connect. I manually added ShadowSocks, ShadowSocks 2022, Glorytun, A Dead Simple VPN and MLVPN keys. Now the router has connected to the VPS and internet works, but I get
Can't contact Server Admin Script (No token yet available)
.The system log repeatedly shows:
Jun 3 20:11:03 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on xx.xx.xx.xx, no server API answer on xx.xx.xx.xx)
Further diagnosis shows omr-admin is probably not running.
On the VPS, I noticed omr-admin kept spiking CPU load and then found it kept continuously restarting.
I then discovered OMR6IN4 cannot start; this might be the culprit?
Result of
journalctl -xeu omr6in4@user0.service
:My diagnosis ended here. This is a fresh installation of the VPS via the provided script:
wget -O - https://www.openmptcprouter.com/server/debian-x86_64.sh | KERNEL="6.1" sh
. Any help is greatly appreciated!Specifications