Closed vinc32 closed 7 months ago
Did you reboot VPS after install ? Why do you set a VPN ?
reboot done - same issue.
I've thought that the ISP (Telekom 5G Germany) may blocks MPTCP Connections - as workaround it said to activate it ;)
Even we MPTCP blocked, it should be able to contact VPS API.
What is the result when you go with a browser to https://curl -k https://<vpsip>:65500/
from the router via SSH ? and curl -k https://127.0.0.1:65500/
from the VPS ?
If no results, what is the result of journalctl -u omr-admin
from the VPS ?
(curl: (7) Failed to connect to 127.0.0.1 port 65500 after 0 ms: Couldn't connect to server
"Welcome to OpenMPTCProuter Server part"root@OpenMPTCProuter:~#
root@localhost:~# journalctl -u omr-admin -- Journal begins at Wed 2021-09-15 09:02:55 UTC, ends at Tue 2024-02-27 16:22:10 UTC. -- Feb 12 08:25:41 localhost systemd[1]: Started OMR-Admin. Feb 25 20:03:03 localhost omr-admin.py[1856564]: /bin/sh: 1: dig: not found Feb 25 20:50:01 localhost systemd[1]: Stopping OMR-Admin... Feb 25 20:50:04 localhost systemd[1]: omr-admin.service: Succeeded. Feb 25 20:50:04 localhost systemd[1]: Stopped OMR-Admin. Feb 25 20:50:04 localhost systemd[1]: omr-admin.service: Consumed 27min 50.544s CPU time. -- Boot 96d3d98e991349f6b2b88102759e5bb7 -- Feb 25 20:50:31 localhost systemd[1]: Started OMR-Admin.
Can you run apt-get install dnsutils && systemctl omr-admin
on the VPS ? At least this fix the dig error.
You are using an IPv4 server IP ?
You remove the VPN on 5G interface ?
systemctl omr-admin -> wasn't found -> not sure how to fix it "E: Unable to locate package omr-admin"
Using IPv4 Server IP Removed VPN on 5G Interface
Just went through install routine and noticed something - VPS running Debian 11 with IONOS Image - used
"wget -O - https://www.openmptcprouter.com/server/debian-x86_64.sh | sh"
To install VPS. Maybe that's the issue?
Sorry it's systemctl restart omr-admin
I have some IONOS VPS and it's working.
Tried - but nothing except OMR-Admin changed.
-- Journal begins at Wed 2021-09-15 09:02:55 UTC, ends at Wed 2024-02-28 16:23:10 UTC. -- Feb 12 08:25:41 localhost systemd[1]: Started OMR-Admin. Feb 25 20:03:03 localhost omr-admin.py[1856564]: /bin/sh: 1: dig: not found Feb 25 20:50:01 localhost systemd[1]: Stopping OMR-Admin... Feb 25 20:50:04 localhost systemd[1]: omr-admin.service: Succeeded. Feb 25 20:50:04 localhost systemd[1]: Stopped OMR-Admin. Feb 25 20:50:04 localhost systemd[1]: omr-admin.service: Consumed 27min 50.544s CPU time. -- Boot 96d3d98e991349f6b2b88102759e5bb7 -- Feb 25 20:50:31 localhost systemd[1]: Started OMR-Admin. Feb 28 09:55:12 localhost systemd[1]: Stopping OMR-Admin... Feb 28 09:55:44 localhost systemd[1]: omr-admin.service: Succeeded. Feb 28 09:55:44 localhost systemd[1]: Stopped OMR-Admin. Feb 28 09:55:44 localhost systemd[1]: omr-admin.service: Consumed 8min 49.436s CPU time. Feb 28 09:55:44 localhost systemd[1]: Started OMR-Admin.
What do you have now in "Status->System log" ? Range 65000-65535 in TCP and UDP, and ICMP are correctly open in Ionos interface ?
Added Ports according Wiki, will try to open everything between 65000-65535
Wed Feb 28 17:02:05 2024 daemon.er glorytun[23137]: %IP%:65001: key exchange failed
Wed Feb 28 17:02:05 2024 daemon.info glorytun|23137): STOPPED tunO
Wed Feb 28 17:02:14 2024 user.notice post-tracking-post-tracking: ompn down because gateway down
Wed Feb 28 17:02:14 2024 user.notice post-tracking-post-tracking: Glorytun VPN down, restart it
Wed Feb 28 17:02:14 2024 daemon.err glorytun[23137]: getpeername: Socket not connected
Wed Feb 28 17:02:14 2024 daemon.notice netifd: Network device 'tun®" link is down
Wed Feb 28 17:02:14 2024 daemon.notice netifd: Interface 'ompn' has link connectivity loss
Wed Feb 28 17:02:14 2024 daemon.notice netifd: Interface 'omrpn' is now down
Wed Feb 28 17:02:14 2024 daemon.notice netifd: Interface 'ompn' is disabled
Wed Feb 28 17:02:14 2024 daemon.info glorytun: starting glorytun von instance vpn
Wed Feb 28 17:02:14 2024 daemon.notice netifd: Interface 'omon' is enabled
Wed Feb 28 17:02:14 2024 daemon.notice netifd: Network device 'tunO" link is up
Wed Feb 28 17:02:14 2024 daemon.notice netifd: Interface 'ompn' has link connectivity
Wed Feb 28 17:02:14 2024 daemon.notice netifd: Interface 'ompn' is setting up now
Wed Feb 28 17:02:14 2024 daemon.info glorytun[1397]: INITIALIZED tunO
Wed Feb 28 17:02:14 2024 daemon.notice netifd: Interface 'omvpn' is now up
Wed Feb 28 17:02:14 2024 daemon.warn [7433]:
There is a problem in this log: interface name omrvon, ompn,... ? tunO, tuno ? You modified it manually ?
not onsite - so copied out of VMware console - so it copied out of a "picture"
Solution found -
5G Router has been the issue - it’s a ZTE MC801A and it’s making the trouble. Changing the APN manually worked.
solution found because I’ve WiFi calling issues inbound behind another one of the same model. Searched for issue and got the hint on sophos forum.
Thanks for the feedback
Thanks for the feedback
Thank you very much for your help! ;) edited closure text
Expected Behavior
Router should connect to VPS getting config via API.
Current Behavior
5G Connection -> Green - showing Public IP VPS -> Not able to connect to Server (Admin Script, no result) -> LOG: "OMR-VPS: Can't get vps token, try later (can ping server vps on %IP%, server API answer on %IP%
Trying to activate VPN Option for 5G Connection -> Gateway Down, No Server ping response.
Log w/o VPN
Tue Feb 27 11:33:42 2024 daemon.err glorytun[18843]: %IP%.65001: connected Tue Feb 27 11:35:01 2024 user.notice OMR-VPS: Can't get vps token, try later (can ping server vpse Feb 27 11:33:52 2024 daemon.info glorytun[18843]: STOPPED tun0 Tue Feb 27 11:34:46 2024 user.notice OMR-VPS: Setting server config error, try again Tue Feb 27 11:35:01 2024 user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on %IP%, no server API answer on %IP%) Tue Feb 27 11:35:01 2024 daemon.info glorytun: starting glorytun vpn instance vpn Tue Feb 27 11:35:01 2024 user.notice omr-bypass: Starting OMR-ByPass... Tue Feb 27 11:35:02 2024 user.notice omr-bypass: OMR-ByPass is running Tue Feb 27 11:35:02 2024 user.notice omr-tracker: Launching... Tue Feb 27 11:35:07 2024 user.notice omr-tracker: Launched Tue Feb 27 11:35:16 2024 user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on %IP%, no server API answer on %IP%)
Log with VPN
ue Feb 27 11:38:51 2024 user.notice omr-bypass: OMR-ByPass is running Tue Feb 27 sp:7fff1cab0860aemon.err glorytun[29713]: getpeername204.65001:ifup of omrvpn11iled Tue Feb 27 11:38:58 2024 daemon.info glorytun[29713]: STOPPED tun0 Tue Feb 27 sp:7fff1cab0860 error:0 in libc.so[7f2dd9787000+49000] Tue Feb 27 11:38:51 2024 user.notice omr-bypass: OMR-ByPass is running Tue Feb 27 11:38:5vps... Tue Feb 27 11:39:12 2024 user.notice mptcp: Reloading mptcpng server vpsvpn9:05 2024 user.notigetpeername: Socket not connected Tue Feb 27 11:39:12 2024 user.notice mptcp: Reloading mptcponfig due to ifup of omrvpn2024 user.notice SQM-autorate: Launch on lan Tue Feb 27 11:39:06 2024 daemon.info glorytun: starting glorytun vpn instance vpn Tue Feb 27 11:39:06 2024 user.notice omr-bypass: Starting OMR-ByPass... Tue Feb 27 1mptcp: Reloading mptcp config due to ifup of omrvpnrunning Tue Feb 27 11:39:10 2024 user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 82.165.112.204, server API answer on 82.165.112.204) Tue Feb 27 11:39:11 2024 user.notice OMR-VPS: Get config from server vps... Tue Feb 27 11:39:11 2024 user.notice OMR-VPS: V2ray restart... Tue Feb 27 11:39:11 2024 user.notice OMR-VPS: Glorytun restart... Tue Feb 27 11:39:11 2024 daemon.err glorytun[29713]: getpeername: Socket not connected Tue Feb 27 11:39:11 2024 daemon.notice netifd: Network device 'tun0' link is down Tue Feb 27 11:39:11 2024 daemon.notice netifd: Interface 'omrvpn' has link connectivity loss Tue Feb 27 11:39:12 2024 user.notice mptcp: Reloading mptcp config duewgwan1 (wgwan1), restart interface Tue Feb 27 11:39:12 2024 user.notice mptcp: Reloading mptcp config due to ifup of omrvpnglorytun: starting glorytun vpn instance vpn Tue Feb 27 11:39:11 2024 user.notice post-tracking-post-tracking: No answer from wgwan1 (wgwan1), restart interface Tue Feb 27 11:39:11 2024 user.notice post-tracking-post-tracking: Set wgwan1 down Tue Feb 27 11:39:11 2024 user.notice OMR-VPS: Glorytun UDP restart... Tsysfs path read for nmptcp config due to ifup of omrvpn12ice 'wgwan1' link is down Tue Feb 27 11:39:11 2024 user.notice OMR-VPS: OpenVPN restart... Tue Feb 27 11:39:11 2024 daemon.notice netifd: Interface 'wgwan1' is now down Tue Feb 27 11:39:11 2024 daemon.notice netifd: Interface 'omrvpn' is enabled Tue FebomrvpnTue Feb 27 11:39:11omrvpnglorytun: starting glorytun vpn instance vpnsetting up now Tue Feb 27 11:39:12 2024 user.notice mptcp: Reloading mptcp config due to ifup of omrvpn11 2024 daemon.notice netifd: Interface 'omrvpn' is setting up now Tue Feb 27 11:39:11 2024 daemon.info glorytun[10052]: INITIALIZED tun0 Tue Feb 27 11:39:11 2024 daemon.notice netifd: Interface 'omrvpn' is now up Tue Feb 27 11:39:12 2024 daemon.warn [7433]: [SQM_IFB_74532] invalid sysfs path read for nmptcp config due to ifup of omrvpn12 2024 user.notice mptcp]: [base-manager] couldn't handle kernel event: device net/SQM_IFB_74532 not found
Tue Feb 27 11:39:12 2024 daemon.warn [7433]: [SQM_IFB_ad945] invalid sysfs path read for net/SQM_IFB_ad945
Tue Feb 27 11:39:12 2024 daemon.warn [7433]: [base-manager] couldn't handle kernel event: device net/SQM_IFB_ad945 not found
Tue Feb 27 11:39:12 2024 user.notice firewall: Reloading firewall due to ifup of omrvpn (tun0)
Tue Feb 27 11:39:12 2024 user.notice mptcp: Reloading mptcp config due to ifup of omrvpnrt firewall reloading
Tue Feb 27 11:39:12 2024 user.notice mptcp: Reloading mptcp config due to ifup of omrvpn (tun0)
Specifications