Replies: 3 comments 8 replies
-
I can't speak for others, but I don't typically use 127.0.0.1 in the config even though I do host and connect locally. I use 0.0.0.0 in network.lua to bind to all interfaces and then connect to a static private IP assigned to my machine. The database uses that IP address. In general, not necessarily specific for this case
If the map server doesn't indicate anything about receiving invalid packets (which would indicate a decryption issue) and you see no other traffic that nobody tried to log in then probably the client couldn't route to the map server If the server actually receives the C2S 0x00A it will look like this (regardless if your client actually loads the zone properly or not):
You could also try turning off new character creation cutscenes, server/settings/default/main.lua Line 111 in 7a46bb1 though I'm not sure that will help. I tested char creation just now and it works fine with it enabled. I only mention it because during char creation the encryption key is incremented for some reason. |
Beta Was this translation helpful? Give feedback.
-
As for your issue, I sometimes get this when making a new character, though not sure what causes it. Have you checked your |
Beta Was this translation helpful? Give feedback.
-
Just to comment, I have solved this now. I did not follow the steps in the |
Beta Was this translation helpful? Give feedback.
-
Just installed a fresh LSB instance locally, followed the the guide to the dot, with three exceptions:
python3
instead ofpy -3
, since it did not recognize that command. Maybe because I already had a Python3 version installed, that did not have it. I doubt this should be an issue, but let me know if it is.Launching it, I can create an account, log in, create a character, but when I try logging into that character, it's stuck on "Downloading data..." for a minute, then it times out with
FFXI-3001
. I read that this may require a few minutes after char creation, so I gave it an hour, with the same result.I verified that the
zone_settings
had127.0.0.1
as the IP, and54230
as the port, which matches what's in thesettings/network.lua
. Since I'm using local access I shouldn't need--hairpin
, but I also tried using it just in case, same result. I also played around withlocalhost
vs127.0.0.1
, since I vaguely remember having issues with this before, although honestly, I'm not even sure that was FFXI related. Fwiw I self-compiledxiloader
from source, but was able to log into a different private server with it, so I doubt this is the issue. If relevant, I used Windower 4.I set
ENABLE_HTTP
totrue
in the network settings, same result. I setUDP_DEBUG
andTCP_DEBUG
totrue
in the network settings, but none of the logs mentioned anything that they didn't mention even without those settings. I did restart all servers between changing the settings file for good measure, even though the map server notified me of the reloaded changes.In possibly related news, I get the same FFXI-3001 issue on an instance set up on our linux server. But before you think this is a "me" issue, a friend is experiencing the same error trying to log into the linux server. If necessary, I can provide some data on that server as well.
I searched around for this issue and found a few things on various Discord servers and one mention in here, but nothing seems to have been resolved. Even if you don't have a proper solution ready, I'd appreciate help on debugging this.
Beta Was this translation helpful? Give feedback.
All reactions