Connectivity Problem with Abiotic Factor - External connection

Technical Support
, ,
1

System Information

Field Value
Operating System Windows - Windows 11 Pro on x86_64
Product AMP ‘Callisto’ v2.5.1.8 (Mainline)
Virtualization None
Application Abiotic Factor
Module GenericModule
Running in Container No
Current State Ready

Problem Description

Issue

Could be me just being dumb, but I am trying to have friends connect externally. I don’t really understand the loop back stuff. I do have the ports forwarded.

Reproduction Steps

  • I am using Abiotic Factor server with default settings and installing the instance.
  • I ensured the proper ports are forwarded with my router.
  • The connection info on the instance is all local. Attempting to use external IP or server browser does not work for connections.
2

@CubeCoders-Bot could you help this user with external connections please. They can connect internally so it’ll either be a port forwarding or a hairpin NAT issue so they’ll need a hand figuring out which is the case.

3

Alright, Blake! Let’s get your friends connected from outside your network. :globe_with_meridians:

From what you’ve shared, it sounds like you’re on the right track with port forwarding. Now, the issue might be related to hairpin NAT or loopback. Here’s a quick way to check what’s what:

  1. Port Forwarding Check: You’ve forwarded ports, but it’s good to verify if they’re working. Use a tool like canyouseeme.org to see if the specific port for Abiotic Factor is reachable from the outside.

  2. Hairpin NAT: If you’re trying to access your own external IP from inside your network, it might not work because of hairpin NAT. To rule this out, have someone outside your network try to connect using your external IP.

Can you let me know what you find when you check these? Then we’ll go from there. :video_game:

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback
4

@CubeCoders-Bot CanYouSeeMe won’t work for UDP since it’s stateless. They’ll need more instruction on how to check what the problem is.

5

Whoops, thanks for jumping in, Mike! :male_detective:

Alright, Blake, let’s take a more detailed dive since UDP can be a bit trickier to test directly.

  1. Double Check Your Router’s Port Forwarding:

    • Ensure both TCP and UDP for the ports needed by Abiotic Factor are forwarded to your local machine’s IP.

  2. Use a Network Tool for Testing:

    • Since direct testing of UDP isn’t feasible, using a utility like Wireshark can help. It’ll allow you to see if inbound traffic hits your network when someone attempts to connect.

  3. External Friend Test:

    • Have a friend outside your network try connecting to your server. If their attempt appears in Wireshark or similar logs, your forwarding is correct, and it’s not reaching the application level.

  4. Check Firewall Settings:

    • Ensure your Windows firewall allows traffic through the forwarded ports for both TCP and UDP.

Give these a shot and see how it goes. If you catch something in Wireshark, it’ll help us pinpoint if the traffic’s getting lost before reaching Abeotic Factor. :satellite:

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback
6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.