#Cannot join my own raid on a remote host

1 messages · Page 1 of 1 (latest)

dull rock
#

So the whole issue.

Friend have a windows server 2022, we gonna name it machine01, he installed
SPT-3.8.1-29197-d3ac83e
and
Fika.Release.0.9.8890.36671

We all have the same release on his machine and mine.
I am in EU he is in the states

Machine01 - Server
Fika server / have public ip
Running Aki.Server

Machine02 - Client
Friend's pc / have public ip
Running Aki. Laucher

Machine03 - Client
My pc / doesn't have public ip
Running Aki. Laucher

Machine04 - Client
Another friend pc / have public ip
Running Aki. Laucher

NOTE: None of the machines are in the same subnet, they don't share lan network.
NOTE: We haven't changed network configurations after the initial setup
NOTE: Machine04 was able to join their own raid and let other people join them with MPT hotfix before
NOTE: I cannot confirm if MPT worked for me

Case 1 - everything works
So i can connect to his server, make a character, play when he starts a raid.

Case 2 - something goes wrong
I am trying to start a raid by myself on his server and i am stuck at Created COOP Game
[ i cannot join my own raid despite that i am connected to his fika server]
My game just stays on that screen right after it says it opens connections to 25565
NOTE: I don't have public IP, so i understand if other people can't join but why i wont be able to join my own raid?

Case 3 - Machine04 joined the server and he tried to host a raid, succeeded once with UPnP error, but then it didn't work again! and they are having public ip, and properly port-forwarded so i am not sure what is going on. they get exactly the same error in their logs as mine

My question here: Is that the issue? That i don't have public IP and when my game starts a session it just dies or is something else wrong here?

Decided to ask because log files giving me strange indication that the connection is instantly closed by the remote host.

Logs on pastebin [the ip is replaced with asteriks for privacy reasons]
https://pastebin.com/uREvWueT

lofty summit
#

Stuck at Created Coop Game means that the connection was not established. You need a public IP as of now to host.

#

We're adding singleplayer later but it doesn't really work well with Fika.

dull rock
#

Thank you for the reply, so yeh that explains my suspicions why i cannot join my raid, but why machine04 have the same issue, sometimes it works, sometimes it doesn't? And they throw exactly same console error despite the fact they have public ip and proper port configured. Any reason what might becausing that?

lofty summit
#

Backend is not doing its job

#

Who is hosting Aki.Server?

dull rock
#

The Machine01, its on its own server, separate network, separate machine
Machine02 player set it up, but everything works for him, however machine01 server and machine02 client don't share the same subnet

#

he enabled on the machine01 port 25565 upd and tcp, 6969 udp and tcp
and he forwarded on his own machine, machine02 25565 udp and tcp

#

the only thing machine01 and machine02 have in common is the same isp [figured might be worth mentioning]

lofty summit
#

Something is blocking 6969 from communicating

#

Every client that wants to click "Host Raid" must have 25565 forwarded.

lofty summit
dull rock
#

Okey, i will check with the host and will personally look at his network config, then i will give an update on the ticket with what i've found and if it works, thank you!

acoustic locust
#

Got it working?

dull rock
#

I was testing local, vpn and direct connection on both 3.8.0 with mpt and 3.8.1 with lastest fika, hence why it took me so much time to reply
Same conditions, same machines, same people, same vpn and subnet.

Client: 14.1.2.29197
STP: SPT-3.8.1-29197-d3ac83e
Fika: Fika.Release.0.9.8892.36315

Conditions: My own aki server, Radmin VPN, firewall off

  • Joining my own aki server: works
  • People joining my aki server: works
  • Me Hosting a raid: doesn't work, i cannot join my own raid [socketexception] seems address translation goes wrong
  • Others hosting a raid: works with upnp error, i can join them if they have upnp on
  • Forcing ip didn't help
  • Setting up upnp didn't help for me

Conditions: Remote aki server, Radmin VPN, firewall off

  • Joining remote aki server: works
  • People joining remote aki server: works
  • Me Hosting a raid: doesn't work
  • Others hosting a raid: works with upnp error or doesn't work, different outcomes without changing the options
  • Forcing vpn ip didn't help
  • Setting up upnp didn't help for me

Conditions: Remote aki server, Direct connection - WAN, firewall off

  • Joining remote aki server: works
  • People joining remote aki server: works
  • Me Hosting a raid: doesn't work
  • Others hosting a raid: works with upnp error or doesn't work, different outcomes without changing the options
  • Setting up upnp didn't help for me
#

Client: 14.1.2.29197
STP: SPT-3.8.0-29197-2dd4d91
Fika: MPT_HOTFIX_2_0.9.8876.41975

Conditions: My own aki server, Radmin VPN, firewall off

  • Joining my own aki server: works
  • People joining my aki server: works
  • Me Hosting a raid: works
  • Others hosting a raid: works

Conditions: Remote aki server, Radmin VPN, firewall off

  • Joining remote aki server: works
  • People joining remote aki server: works
  • Me Hosting a raid: works
  • Others hosting a raid: works

Conditions: Remote aki server, Direct connection - WAN, firewall off

  • Joining remote aki server: works
  • People joining remote aki server: works
  • Me Hosting a raid: ---untested---
  • Others hosting a raid: works

Testing the old stp with the old fika release everything works as expected, without an issue, testing the new one, it works only on localhost. What have you changed guys?

lofty summit
#

Literally nothing changed

#

3.8.1 has a new http.json from SPT, did you update that as instructed in FAQ?

dull rock
#

mhm,.. maybe spt is the cause and not fika, unsure, i will have to look at the src

#

they are using litenetlib developed by revenantx for the Aki project, i know that revenantx said before there was issues with 3g/4g routers and udp hole punching, so maybe the updated aki server is the reason

lofty summit
#

We do not use UDP hole punching

#

My friend plays and hosts on a 4g router

#

Aki does not use LiteNetLib, we do.

dull rock
#

i thought aki did, i am sorry, its a very modular project, like i said haven't looked at the source, just was testing the different versions to see what will happen

#

any advice or any steps i can do to produce some logs or anything... to trace back to what might be causing it?

lofty summit
#

So

#

I'm trying to understand your original issue, can you not connect to yourself while hosting?

#

The Aki.Server?

dull rock
#

if i am hosting aki server on lan, locally on 127.0.0.1 or 0.0.0.0 i can connect and i can start a raid
if other person is hosting aki on a different network, i can join the aki server, but i cannot start a raid, i can only join raids [other people with public ip and not being behind nat had same issue]

if i am hosting aki server on vpn layer 2, global tunneling, i am setting up the vpn ip on aki, i can join aki, other people can join aki, i cannot join my own raid, no matter if i force the vpn ip or not, other people can host a raid but they are getting upnp error, but it works

lofty summit
#

Did you disable UPnP while using a vPN?

#

The UPnP error only shows if you have it enabled.

#

It should never be enabled with a VPN

dull rock
#

maybe my router is the issue

lofty summit
#

Force + Bind IP as your VPN IP

dull rock
#

i did that, but i will try again with the last fika release and give you an update [on the bright side in a month i am getting a new router, i will be able to confirm if its the router itself]

dull rock
#

as soon as i can, thank you for the support thou

#

so itseems i had to reflash my router firmware, previously i've tried that and it didn't work, old version have upnp issues

#

thanks tplink, 3 days been looking into that ughhhhh

lofty summit
#

So it works now?

dull rock
#

same settings for vpn as before, all i did is reflash the mr6400 firmware with the last version, turn off upnp again and it worked

#

still not sure whats the difference between old and new version, but i guessit works, i will test it with other people to see if it will work