Authentication Problem
Authentication Problem
I setup a local user on my server with the following commands
LOCAL_USER TestOwner password
USER_LEVEL TestOwner@ 0
When I try to login from the chat by typing /login TestOwner@ ( also tried without the @ ) and filling out the popup form with TestOwner and the password I get the following error message
Login failed, reason: Server address mismatch, aaa.bbb.ccc.ddd:4534 (sent by client) != aaa.bbb.ccc.dd:52711 (our address). Pharming suspected. If you are connection from the LAN and get this error, either set "TRUST_LAN" on the server (only if your LAN can be fully trusted, of course) or use "SERVER_IP" to make the local IP known to the server.
Can you help me with this please, thanks.
LOCAL_USER TestOwner password
USER_LEVEL TestOwner@ 0
When I try to login from the chat by typing /login TestOwner@ ( also tried without the @ ) and filling out the popup form with TestOwner and the password I get the following error message
Login failed, reason: Server address mismatch, aaa.bbb.ccc.ddd:4534 (sent by client) != aaa.bbb.ccc.dd:52711 (our address). Pharming suspected. If you are connection from the LAN and get this error, either set "TRUST_LAN" on the server (only if your LAN can be fully trusted, of course) or use "SERVER_IP" to make the local IP known to the server.
Can you help me with this please, thanks.
Last edited by LoveBug on Sat Jul 30, 2011 2:19 pm, edited 1 time in total.
Re: local authentication problem
Login failed, reason: Server address mismatch, aaa.bbb.ccc.ddd:4534 (sent by client) != aaa.bbb.ccc.dd:52711 (our address). Pharming suspected. If you are connection from the LAN and get this error, either set "TRUST_LAN" on the server (only if your LAN can be fully trusted, of course) or use "SERVER_IP" to make the local IP known to the server.
Re: local authentication problem
ive tried it from the same lan and from outside on a different ip and still I get the same error message
Re: local authentication problem
Have you you used SERVER_IP or TRUST_LAN? It won't work without.
Re: local authentication problem
I tried trust_lan 1 and that didnt help i still got the same error message
I dont understand the server_ip could you explain what I have to do
Is that something I type local or something I add to the server config ?
I dont understand the server_ip could you explain what I have to do
Is that something I type local or something I add to the server config ?
Re: local authentication problem
just to eliminate a potential error: trust_lan also needs to be set on the server.
As does server_ip. If you don't have talk_to_master enabled (which lets the server find its IP on its own), you need to put
server_ip <ip of the server>
into your server configuration.
As does server_ip. If you don't have talk_to_master enabled (which lets the server find its IP on its own), you need to put
server_ip <ip of the server>
into your server configuration.
Re: local authentication problem
I do have talk_to_master 1 in the configs and my server shows up in the master list, I can also connect to it from a different location/ip and play but I cannot login
For a test I ran a duplicate server from home with talk_to_master 0 and ran the client on the same computer, I could see the server in the multiplayer lan option, connected and could login no problem
So it seems that I can only login from a client running on the same computer as the server, if I login from a client on a different computer thats either on the same lan or on another ip from outside I can only play but cannot login
For a test I ran a duplicate server from home with talk_to_master 0 and ran the client on the same computer, I could see the server in the multiplayer lan option, connected and could login no problem
So it seems that I can only login from a client running on the same computer as the server, if I login from a client on a different computer thats either on the same lan or on another ip from outside I can only play but cannot login
Re: local authentication problem
Hmm, could you post full server logs, then? And tell us which server you're talking about so we can check master logs and try to connect to it?
Re: local authentication problem
The server is called TEMPEST U.K. Open Play StyleZ-Man wrote:Hmm, could you post full server logs, then? And tell us which server you're talking about so we can check master logs and try to connect to it?
Im not sure how to enable server logs ? could you tell me how to enable them and where the log files will be stored thanks
Re: local authentication problem
If you're using our /etc/init.d starter scripts, logs are already in /var/log/armagetronad_dedicated.log.
If you're using anything else... well, the server puts the logs out to standard output. That needs to be saved or just copied over. I just need the first bits after the server starts up, the part where it communicates with the masters.
If you're using anything else... well, the server puts the logs out to standard output. That needs to be saved or just copied over. I just need the first bits after the server starts up, the part where it communicates with the masters.
Re: local authentication problem
thanks i'll take a look and post what I find
-
- On Lightcycle Grid
- Posts: 37
- Joined: Tue Jan 08, 2008 1:40 pm
Re: local authentication problem
I don't get why it says port 62238. This is not a port usually used by Armagetron. Unless there is something I don't know, and that is not documented on the wiki.
Try put
SERVER_PORT 4534
in your server_info.cfg file.
Try put
SERVER_PORT 4534
in your server_info.cfg file.
Re: local authentication problem
It's the random port used in client mode. Usually, servers communicate with the master using the server socket, but if that fails, they resort to the client socket. That's why I want to see the master communication, to maybe see whether that is happening, and if yes, why.superkikim wrote:I don't get why it says port 62238.
Re: local authentication problem
That is the first command in my settings_custom.cfgsuperkikim wrote:I don't get why it says port 62238. This is not a port usually used by Armagetron. Unless there is something I don't know, and that is not documented on the wiki.
Try put
SERVER_PORT 4534
in your server_info.cfg file.
I dont have it in server_info.cfg does that make any difference ?
All my server configs are in settings_custom.cfg except for the users which I have in settings_user.cfg which is loaded by sinclude settings_user.cfg command in my autoexec.cfg
-
- Posts: 5
- Joined: Sun Jun 19, 2011 7:16 pm
Re: local authentication problem
Bitwise here,
I have checked out my master server cache and it appears that it reports the server to the masters as
94.193.96.32:4534, however on authentication (not just locally, globally as well) it reports back a random
port for some reason and reports it suspects pharming. The ports change on server restart
I have no clue on why the server reports a random port to the client on auth, however it reports the right
port to masters...
Full error:
Click here for image
I have checked out my master server cache and it appears that it reports the server to the masters as
94.193.96.32:4534, however on authentication (not just locally, globally as well) it reports back a random
port for some reason and reports it suspects pharming. The ports change on server restart
I have no clue on why the server reports a random port to the client on auth, however it reports the right
port to masters...
Full error:
Click here for image