System Information
Field |
Value |
Operating System |
Linux - Debian GNU/Linux 12 on x86_64 |
Product |
AMP ‘Phobos’ v2.6.0.12 (Mainline) |
Virtualization |
QEMU_KVM |
Application |
Minecraft |
Module |
MinecraftModule |
Running in Container |
No |
Current State |
Ready |
Problem Description
Issue
user is unable to connect to server via wifi, but is able to connect via hotspot
firewall is set up with correct ports on server
tried multiple things:
- specifying port number
- added exception for user’s firewall
- confirmed user able to connect to other servers on wifi
- followed diagnosing connectivity issues checklist
Reproduction Steps
- launch server
- attempt to connect via wifi
- receive unknown host error
- switch connection to hotspot
- able to connect to server
Have them put in the IP instead of the domain name and see if that works. Could just be a DNS issue on the user’s end
If the user is on the same network as the server then it is likely a NAT hairpin issue
Greelan, user is not on the same network, the server is hosted via hostinger
ThePotatoKing, I can do this with the current player as I trust him, but we are planning on branching out soon to other player(s) that I won’t fully trust for a while. If this fixes the issue for him, great, but how would I go about helping him and other player(s) confirm and resolve DNS issues?
Sorry if it’s a dumb question, I usually only self-host for a small group of friends, so I’ve never had these kind of issues…
You can use any domain name and see the IP behind it, there’s no reason to be worried about trusting the user (in other words, domains/subdomains do not hide the IP)
Also note, this is the forum for AMP and not Hostinger support, so no clue as to why Hostinger’s DNS just doesn’t work correctly for some ISPs. (Hostinger may know more on the topic)
@ThePotatoKing, user tried IP. Result was different, but still unable to connect. User sees a red “X” and “1.21” over the ping status when viewing servers to connect to. Will try to work with Hostinger to resolve the issue unless you have any other ideas/suggestions?
Could double check that it’s the same IP that Hostinger gave your for your VPS, in case there was a typo