Gunsight1 Posted October 6, 2015 Posted October 6, 2015 Tried to log in and play today and all I get after clicking to connect with my steam account is a notice saying: Error: Login queue request failed. It shows people are online on the count at the bottom of the screen, but no go on getting in 1
Henrik Posted October 6, 2015 Posted October 6, 2015 http://forum.game-labs.net/index.php?/topic/7267-no-steam-id/#entry137182 Perhaps it's a steam issue? Sorry cannot help you any further but hope it gets resolved soon for you!
Henry d'Esterre Darby Posted October 6, 2015 Posted October 6, 2015 Gunsight, Steam's Login API well.....isn't very good. For such a mission critical system, it's down far too often. Please post here if your problem is still not resolved. Rebooting your computer to clean up the Steam Login may help too.
Gunsight1 Posted October 6, 2015 Author Posted October 6, 2015 Ok. I'll give it a shot when I get home from work this evening.. Is there a way to login without a steam login?
Henry d'Esterre Darby Posted October 6, 2015 Posted October 6, 2015 No, Steam is the only way to log in, and there are no other alternative login schemes that have been announced.
Gunsight1 Posted October 6, 2015 Author Posted October 6, 2015 Good to know. Will report back with results from my attempt tonight.
Arnaud Arpes Posted October 7, 2015 Posted October 7, 2015 I haven't been able to log in now for two days straight. All attempts result in various errors. Is anyone else still having trouble logging in?
Gunsight1 Posted October 7, 2015 Author Posted October 7, 2015 Well, today is an entirely new problem. Now when I try to launch the game I just get a black screen for a while, then the game stops responding and I have to force close it. May just reinstall.
Henrik Posted October 7, 2015 Posted October 7, 2015 (edited) Think that is your only option at this point, do hope it gets resolved though! Edited October 7, 2015 by Henrik
Henry d'Esterre Darby Posted October 7, 2015 Posted October 7, 2015 Reinstall is pretty quick, but yes, that would be a good next step. Sorry to hear you're still having issues. Keep posting what you're trying and we'll keep making suggestions.
avasyliev Posted October 7, 2015 Posted October 7, 2015 Gunsight1, please try complete deleting of game files (..\Steam\steamapps\common\Naval Action) and reinstall game afterwards. If problem will still happen, please send logs and error information to us using Manual crash reporting system (please see details by link: http://forum.game-labs.net/index.php?/topic/2892-technical-problems-reporting-guide-known-issues-and-their-solutions )
Shannelle Posted October 8, 2015 Posted October 8, 2015 Tried deleting and reinstalling, no joy. Still login issues. Every 5 tries I get into the game but it doesn't work and it just bombs out. Something is wrong can we get some help???? 1
avasyliev Posted October 8, 2015 Posted October 8, 2015 Tried deleting and reinstalling, no joy. Still login issues. Every 5 tries I get into the game but it doesn't work and it just bombs out. Something is wrong can we get some help???? Please write your in-game player name so that we can try to analyze logs Also, please check your network and firewall settings, if the following ports are open: http://forum.game-labs.net/index.php?/topic/2892-technical-problems-reporting-guide-known-issues-and-their-solutions/#entry135352
Arnaud Arpes Posted October 10, 2015 Posted October 10, 2015 (edited) Please write your in-game player name so that we can try to analyze logs Also, please check your network and firewall settings, if the following ports are open: http://forum.game-labs.net/index.php?/topic/2892-technical-problems-reporting-guide-known-issues-and-their-solutions/#entry135352 I've been able to log into the game once in the past week that I've tried. I've tried 5 or 6 different days to log in. My in-game name is Arnaud Arpes I had been playing the game fine for over a month before this. I've reinstalled, and made sure all the necessary ports are open, even turned off firewall completely. Additionally I created Inbound Rules for client.exe to allow any port necessary. Edited October 10, 2015 by Arnaud Arpes
Arnaud Arpes Posted October 10, 2015 Posted October 10, 2015 (edited) You have restarted steam? Yes, I have: 1) Restarted Steam 2) Uninstalled Game & Reinstalled 3) Created Inbound/Outbound Rules for all ports and for client.exe 4) Taken all my other in-home devices off wifi/ethernet. 5) Tried logging in each day for about a week. Always failing to actually get in game. Either I error out on the login, or Error out and get returned to login when choosing Character and pressing Start. EDIT: Today I made it into the game without any issue. This is the second time in a week I've been able to log in and make it into actual OW Sailing. Edited October 10, 2015 by Arnaud Arpes
Henry d'Esterre Darby Posted October 10, 2015 Posted October 10, 2015 Interesting. What is different about today?
yamms Posted October 11, 2015 Posted October 11, 2015 had the same issue. done all of the steps - works for a few minutes then cuts out. then most of the time it doesn't log in at all.
Arnaud Arpes Posted October 11, 2015 Posted October 11, 2015 (edited) Interesting. What is different about today? Nothing that I know of. I played for about 45 minutes, was in my 2nd battle of the day and the game sent me back to the login screen without error or warning. Now, I'm back to being unable to log in. When I do get in, I'm in the Port screen for Plymouth, there is no chat tabs, no player messages are visible, I can click and switch between my ships but pressing Sail does nothing. Checked the game's logs, found this: 1664:[2015-Oct-10 22:53:35.460200] Log: [10/11/2015 3:53:35 AM] SendWebRequest: error while getting response from http://89.163.234.93:7770/queueListener/: couldn't connect to host However, just the attempt before it was successful: 1664:[2015-Oct-10 22:53:12.436200] Log: [10/11/2015 3:53:12 AM] SendWebRequest: received response from http://89.163.234.93:7770/queueListener/: { Ran a 'tracert' to the IP given in the logs. It completed the route, with some intermittent *'s. I saw it took a route through Cogent. Checked 'Internet Health Report' and saw Cogent had Critical > 180ms Latency. So possibly this is the cause? Shitty backbone issues. I'll check again when I see the cogent issues resolved and see if that's the difference. FOLLOWUP: I checked this morning and Cogent's issues were resolved it looked like. So I ran another ping and tracert to the IP 89.163.234.93. No timeouts this time. Tried logging into the game, made it in first try fast as a snap. So it does seem to be network related. I recommend anyone having issues logging into the game try the following steps: 1) Open up Windows Command Prompt 2) type in 'tracert 89.163.234.93' and let it run. Keep an eye out for any '*' symbols or request timed outs. Allow the trace to finish. 3) Once it completes, run the following: ping 89.163.234.93 if it times out, take note. 4) Look to see the names of the servers that gave the * * symbols in the tracert. Check here: http://internethealthreport.com/and see if there is any issue relating to the server hop that had issues. If there is, this is likely why. Edited October 11, 2015 by Arnaud Arpes 1
NorthernWolves Posted October 12, 2015 Posted October 12, 2015 I'm having a nightmare the past week, booted left and right and can't log back in. I can't play like this. I've f11'd several times, sent multiple crash reports. Tonight I was kicked and tried for over 30 minutes to get back in. I ran speedtest.net, 95mb download, not a problem on my end. It's not just me, I see the players online drop by 20-30 at a time when this happens. 1
avasyliev Posted October 12, 2015 Posted October 12, 2015 I'm having a nightmare the past week, booted left and right and can't log back in. I can't play like this. I've f11'd several times, sent multiple crash reports. Tonight I was kicked and tried for over 30 minutes to get back in. I ran speedtest.net, 95mb download, not a problem on my end. It's not just me, I see the players online drop by 20-30 at a time when this happens. Please try testing connection to game server server using tracert to 89.163.234.93, as described by the following link: http://forum.game-labs.net/index.php?/topic/2892-technical-problems-reporting-guide-known-issues-and-their-solutions/?p=135352 Please copy-paste results provided by utility here so that we can analyze the problem. 1
Arnaud Arpes Posted October 13, 2015 Posted October 13, 2015 (edited) Tracing route to 89.163.234.93 over a maximum of 30 hops 1 5 ms 1 ms 1 ms homeportal [192.168.1.254] 2 6 ms 8 ms 3 ms 75-1-192-3.lightspeed.snantx.sbcglobal.net [75.1.192.3] 3 7 ms 3 ms 5 ms 75.28.192.128 4 12 ms 8 ms 4 ms 12.83.39.13 5 14 ms 16 ms 15 ms ggr3.dlstx.ip.att.net [12.122.139.17] 6 13 ms 12 ms 12 ms 192.205.36.222 7 13 ms 15 ms 12 ms be2032.ccr22.dfw01.atlas.cogentco.com [154.54.6.53] 8 24 ms 22 ms 22 ms be2433.ccr22.mci01.atlas.cogentco.com [154.54.3.214] 9 38 ms 36 ms 35 ms be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.118] 10 47 ms 44 ms 43 ms be2185.ccr22.cle04.atlas.cogentco.com [154.54.43.178] 11 * 80 ms 81 ms be2597.ccr22.yyz02.atlas.cogentco.com [154.54.31.90] 12 82 ms 82 ms 83 ms be2093.ccr22.ymq02.atlas.cogentco.com [154.54.44.106] 13 149 ms 148 ms 149 ms be2385.ccr22.lpl01.atlas.cogentco.com [154.54.44.142] 14 163 ms * 162 ms be2183.ccr42.ams03.atlas.cogentco.com [154.54.58.70] 15 * 168 ms 167 ms be2440.agr21.ams03.atlas.cogentco.com [130.117.50.6] 16 * 172 ms * be2114.rcr21.dus01.atlas.cogentco.com [130.117.48.62] 17 173 ms 175 ms 174 ms be2567.nr11.b015770-1.dus01.atlas.cogentco.com [154.25.6.182] 18 * 170 ms 172 ms 149.6.138.122 19 165 ms 164 ms * 89.163.234.93 20 165 ms 165 ms 165 ms 89.163.234.93Trace complete.&&ping 89.163.234.93Pinging 89.163.234.93 with 32 bytes of data:Reply from 89.163.234.93: bytes=32 time=166ms TTL=106Reply from 89.163.234.93: bytes=32 time=168ms TTL=106Reply from 89.163.234.93: bytes=32 time=165ms TTL=106Request timed out.Ping statistics for 89.163.234.93: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),Approximate round trip times in milli-seconds: Minimum = 165ms, Maximum = 168ms, Average = 166ms__________I've been having the issue still, though it's been slightly less often than before. I'm experiencing it currently, and so I grabbed a tracert and ping just to provide in hopes that it may help devs, myself and others determine the cause. Edited October 13, 2015 by Arnaud Arpes
NorthernWolves Posted October 13, 2015 Posted October 13, 2015 Please try testing connection to game server server using tracert to 89.163.234.93, as described by the following link: http://forum.game-labs.net/index.php?/topic/2892-technical-problems-reporting-guide-known-issues-and-their-solutions/?p=135352 Please copy-paste results provided by utility here so that we can analyze the problem. Ok will do, thanks Update: Let me add that at no time during these issues was my ping higher than normal. Also this confused me: " Type: tracert <server_address> and press enter (<server_address> is actual address of game server)" so if it confuses anyone else type this exactly: tracert 89.163.234.93 Tracing route to 89.163.234.93 over a maximum of 30 hops 1 7 ms 6 ms 2 ms 10.0.0.1 2 * * * Request timed out. 3 25 ms 24 ms 29 ms xe-4-0-1-0-sur04.or.comcast.ne t [68.85.242.109] 4 19 ms 17 ms 23 ms ae-51-0-ar01.or.comcast.net [6 8.87.216.105] 5 23 ms 18 ms 36 ms be-33490-cr02.seattle.wa.ibone.comcast.net [68.8 6.92.217] 6 20 ms 19 ms 19 ms he-0-13-0-0-pe04.seattle.wa.ibone.comcast.net [6 8.86.82.234] 7 20 ms 24 ms 39 ms as174.seattle.wa.ibone.comcast.net [66.208.228.1 10] 8 53 ms 57 ms 56 ms be2085.ccr21.slc01.atlas.cogentco.com [154.54.2. 198] 9 53 ms 60 ms 64 ms be2127.ccr22.den01.atlas.cogentco.com [154.54.25 .69] 10 83 ms 72 ms 80 ms be2130.ccr22.mci01.atlas.cogentco.com [154.54.26 .122] 11 79 ms 79 ms 77 ms be2157.ccr42.ord01.atlas.cogentco.com [154.54.6. 118] 12 86 ms 89 ms 104 ms be2185.ccr22.cle04.atlas.cogentco.com [154.54.43 .178] 13 98 ms 102 ms 101 ms be2597.ccr22.yyz02.atlas.cogentco.com [154.54.31 .90] 14 113 ms 102 ms 106 ms be2093.ccr22.ymq02.atlas.cogentco.com [154.54.44 .106] 15 170 ms 169 ms 179 ms be2385.ccr22.lpl01.atlas.cogentco.com [154.54.44 .142] 16 179 ms 197 ms 176 ms be2183.ccr42.ams03.atlas.cogentco.com [154.54.58 .70] 17 180 ms 187 ms 181 ms be2440.agr21.ams03.atlas.cogentco.com [130.117.5 0.6] 18 189 ms 185 ms 184 ms be2114.rcr21.dus01.atlas.cogentco.com [130.117.4 8.62] 19 186 ms 191 ms 184 ms be2567.nr11.b015770-1.dus01.atlas.cogentco.com [ 154.25.6.182] 20 196 ms 197 ms 185 ms 149.6.138.122 21 184 ms 182 ms 185 ms 89.163.234.93 Trace complete. >ping 89.163.234.93 Pinging 89.163.234.93 with 32 bytes of data: Reply from 89.163.234.93: bytes=32 time=189ms TTL=108 Reply from 89.163.234.93: bytes=32 time=188ms TTL=108 Reply from 89.163.234.93: bytes=32 time=191ms TTL=108 Reply from 89.163.234.93: bytes=32 time=181ms TTL=108 Ping statistics for 89.163.234.93: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 181ms, Maximum = 191ms, Average = 187ms 1
Arnaud Arpes Posted October 13, 2015 Posted October 13, 2015 Ok will do, thanks Update: Let me add that at no time during these issues was my ping higher than normal. Also this confused me: " Type: tracert <server_address> and press enter (<server_address> is actual address of game server)" so if it confuses anyone else type this exactly: tracert 89.163.234.93 Tracing route to 89.163.234.93 over a maximum of 30 hops 1 7 ms 6 ms 2 ms 10.0.0.1 2 * * * Request timed out. 3 25 ms 24 ms 29 ms xe-4-0-1-0-sur04.or.comcast.ne t [68.85.242.109] 4 19 ms 17 ms 23 ms ae-51-0-ar01.or.comcast.net [6 8.87.216.105] 5 23 ms 18 ms 36 ms be-33490-cr02.seattle.wa.ibone.comcast.net [68.8 6.92.217] 6 20 ms 19 ms 19 ms he-0-13-0-0-pe04.seattle.wa.ibone.comcast.net [6 8.86.82.234] 7 20 ms 24 ms 39 ms as174.seattle.wa.ibone.comcast.net [66.208.228.1 10] 8 53 ms 57 ms 56 ms be2085.ccr21.slc01.atlas.cogentco.com [154.54.2. 198] 9 53 ms 60 ms 64 ms be2127.ccr22.den01.atlas.cogentco.com [154.54.25 .69] 10 83 ms 72 ms 80 ms be2130.ccr22.mci01.atlas.cogentco.com [154.54.26 .122] 11 79 ms 79 ms 77 ms be2157.ccr42.ord01.atlas.cogentco.com [154.54.6. 118] 12 86 ms 89 ms 104 ms be2185.ccr22.cle04.atlas.cogentco.com [154.54.43 .178] 13 98 ms 102 ms 101 ms be2597.ccr22.yyz02.atlas.cogentco.com [154.54.31 .90] 14 113 ms 102 ms 106 ms be2093.ccr22.ymq02.atlas.cogentco.com [154.54.44 .106] 15 170 ms 169 ms 179 ms be2385.ccr22.lpl01.atlas.cogentco.com [154.54.44 .142] 16 179 ms 197 ms 176 ms be2183.ccr42.ams03.atlas.cogentco.com [154.54.58 .70] 17 180 ms 187 ms 181 ms be2440.agr21.ams03.atlas.cogentco.com [130.117.5 0.6] 18 189 ms 185 ms 184 ms be2114.rcr21.dus01.atlas.cogentco.com [130.117.4 8.62] 19 186 ms 191 ms 184 ms be2567.nr11.b015770-1.dus01.atlas.cogentco.com [ 154.25.6.182] 20 196 ms 197 ms 185 ms 149.6.138.122 21 184 ms 182 ms 185 ms 89.163.234.93 Trace complete. >ping 89.163.234.93 Pinging 89.163.234.93 with 32 bytes of data: Reply from 89.163.234.93: bytes=32 time=189ms TTL=108 Reply from 89.163.234.93: bytes=32 time=188ms TTL=108 Reply from 89.163.234.93: bytes=32 time=191ms TTL=108 Reply from 89.163.234.93: bytes=32 time=181ms TTL=108 Ping statistics for 89.163.234.93: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 181ms, Maximum = 191ms, Average = 187ms Interesting, seems we take the same route through Cogent to reach the server. Were you experiencing login issues at the specific time you took the tracert? I've noticed that anytime my pings have no packetloss/timeouts it's typically working. So much so that I've started running pings before I try logging into the game even.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now