-
-
Notifications
You must be signed in to change notification settings - Fork 252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues getting Connection between VPS / Router #3184
Comments
Did you reboot VPS after install ? |
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. |
browser to https://:65500/
curl -k https://127.0.0.1:65500/ from VPS(curl: (7) Failed to connect to 127.0.0.1 port 65500 after 0 ms: Couldn't connect to server curl -k https://:65500/ from Router"Welcome to OpenMPTCProuter Server part"root@OpenMPTCProuter:~# journalctl -u omr-adminroot@localhost:~# journalctl -u omr-admin |
Can you run |
systemctl omr-admin -> wasn't found -> not sure how to fix it Using IPv4 Server IP Just went through install routine and noticed something - VPS running Debian 11 with IONOS Image - used To install VPS. Maybe that's the issue? |
Sorry it's |
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. -- |
What do you have now in "Status->System log" ? |
Wed Feb 28 17:02:05 2024 daemon.er glorytun[23137]: %IP%:65001: key exchange failed |
There is a problem in this log: interface name omrvon, ompn,... ? tunO, tuno ? |
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. 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 |
Thank you very much for your help! ;) |
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
The text was updated successfully, but these errors were encountered: