Forums » Bugs
Cannot conect to server
Is the game down? I was launching from a station in Arta C, the game froze mid launch and now I cannot reconnect to the server.
Realising this is not the same issue, I think this topic is the best place to report this.
Every time I connect, I get the following errors.
Connecting to cloud.patchstorm.com:21024...
getaddrinfo error: Name or service not known
Failed connecting to cloud.patchstorm.com
Unable to resolve server name to an IP address.
Connecting to update2.vendetta-online.com:21024...
Latest version: vendetta-1.8.430
Version is current; verifying files...
Connecting to cloud.patchstorm.com:21024...
getaddrinfo error: Name or service not known
Failed connecting to cloud.patchstorm.com
Unable to resolve server name to an IP address.
Connecting to update2.vendetta-online.com:21024...
Welcome to Vendetta Online 1.8.430
Is anyone else having this problem?
Every time I connect, I get the following errors.
Connecting to cloud.patchstorm.com:21024...
getaddrinfo error: Name or service not known
Failed connecting to cloud.patchstorm.com
Unable to resolve server name to an IP address.
Connecting to update2.vendetta-online.com:21024...
Latest version: vendetta-1.8.430
Version is current; verifying files...
Connecting to cloud.patchstorm.com:21024...
getaddrinfo error: Name or service not known
Failed connecting to cloud.patchstorm.com
Unable to resolve server name to an IP address.
Connecting to update2.vendetta-online.com:21024...
Welcome to Vendetta Online 1.8.430
Is anyone else having this problem?
Dilan, what kind of computer or device are you using to play?
And, what kind of network are you using? Cellular? What carrier?
And, what kind of network are you using? Cellular? What carrier?
Gigabyte Q1542. Running Fedora Server 25, with workstation installed. Carrier at the moment is Vodacom.
What are you using for a Domain Name Server?
Have you tried using 8.8.8.8 (google's DNS), out of curiosity?
Have you tried using 8.8.8.8 (google's DNS), out of curiosity?
I am using the dns as provided by vodacom
pri: 196.207.35.29
sec: 41.1.114.13
type 3G
pri: 196.207.35.29
sec: 41.1.114.13
type 3G
Well, what happens when you try doing a "dig cloud.patchstorm.com"? It appears there's some kind of basic DNS failure happening here.
ping cloud.patchstorm.com
ping: cloud.patchstorm.com: Name or service not known
-----------------------------------------------------------------------------------------------------
dig cloud.patchstorm.com
; <<>> DiG 9.10.5-P2-RedHat-9.10.5-2.P2.fc25 <<>> cloud.patchstorm.com
;; global options: +cmd
;; connection timed out; no servers could be reached
-----------------------------------------------------------------------------------------------------
When trying a few min later, i got the following result.
-----------------------------------------------------------------------------------------------------
dig cloud.patchstorm.com
; <<>> DiG 9.10.5-P2-RedHat-9.10.5-2.P2.fc25 <<>> cloud.patchstorm.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 45242
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;cloud.patchstorm.com. IN A
;; Query time: 708 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Fri Sep 15 18:54:59 SAST 2017
;; MSG SIZE rcvd: 49
-----------------------------------------------------------------------------------------------------
Fails half the time, and on occation I have to re start the VO update utility as it got no responce from the VO servers.
Dilan
ping: cloud.patchstorm.com: Name or service not known
-----------------------------------------------------------------------------------------------------
dig cloud.patchstorm.com
; <<>> DiG 9.10.5-P2-RedHat-9.10.5-2.P2.fc25 <<>> cloud.patchstorm.com
;; global options: +cmd
;; connection timed out; no servers could be reached
-----------------------------------------------------------------------------------------------------
When trying a few min later, i got the following result.
-----------------------------------------------------------------------------------------------------
dig cloud.patchstorm.com
; <<>> DiG 9.10.5-P2-RedHat-9.10.5-2.P2.fc25 <<>> cloud.patchstorm.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 45242
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;cloud.patchstorm.com. IN A
;; Query time: 708 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Fri Sep 15 18:54:59 SAST 2017
;; MSG SIZE rcvd: 49
-----------------------------------------------------------------------------------------------------
Fails half the time, and on occation I have to re start the VO update utility as it got no responce from the VO servers.
Dilan
Have you tried using openDNS or googleDNS instead? Is your router or your PC on 192.168.0.1 ?
Yeah, I would suggest trying a different nameserver setup as well, like Google's 8.8.8.8 that I mentioned earlier.
Basically, you're experiencing a DNS lookup failure, and if you're actually seeing it on *both* VO server clouds ("primary" cloud.patchstorm.com and "fallback" update2.vendetta-online.com).. then that's probably an issue on your end.
There shouldn't be issues with either.. but DNS for the first is hosted by a professional DNS shop, and the fallback is an independent pair of Bind9 nameservers run by me.. the likelihood of both of them having an issue at the same time is extremely low.
As Yoda points out, your actual DNS lookup seems to be using 192.168.0.1, as opposed to those nameservers you mentioned above, so if that machine isn't doing a proper job of being a DNS proxy, or whatever, then that could be part of the issue.
Basically, you're experiencing a DNS lookup failure, and if you're actually seeing it on *both* VO server clouds ("primary" cloud.patchstorm.com and "fallback" update2.vendetta-online.com).. then that's probably an issue on your end.
There shouldn't be issues with either.. but DNS for the first is hosted by a professional DNS shop, and the fallback is an independent pair of Bind9 nameservers run by me.. the likelihood of both of them having an issue at the same time is extremely low.
As Yoda points out, your actual DNS lookup seems to be using 192.168.0.1, as opposed to those nameservers you mentioned above, so if that machine isn't doing a proper job of being a DNS proxy, or whatever, then that could be part of the issue.
In reply to both yoda, and Incarnate, 192.168.0.1 is the ip of my 3g wifi router. As of yesterday, that router failed completely. I switched to the mobile hotspot on the tablet, and i am still getting the same connection error messages.
Weird. If I change to the DNS servers you mention (they are actually public DNS servers hosted by vodocom) I still get no error which would point to something badly configured on your actual laptop. I notice you are using Fedora server 25, do you have Bind9 installed and if so is the named service running?
Have you messed with anything related to Bind or DNS, like setting up a web server with your own domain or anything? Anyway, I would definitely say at this point that there is a problem with either your setup, or your connection.
Have you messed with anything related to Bind or DNS, like setting up a web server with your own domain or anything? Anyway, I would definitely say at this point that there is a problem with either your setup, or your connection.
Had httpd installed, was not aware Bind was installed. Removed both. Tried the connection again, and still the same issue. So I restarted the laptop, and tried again. Problem is persisting.
Connecting to cloud.patchstorm.com:21024...
getaddrinfo error: Name or service not known
Failed connecting to cloud.patchstorm.com
Unable to resolve server name to an IP address.
Connecting to update2.vendetta-online.com:21024...
Latest version: vendetta-1.8.431
Version is current; verifying files...
Connecting to cloud.patchstorm.com:21024...
getaddrinfo error: Name or service not known
Failed connecting to cloud.patchstorm.com
Unable to resolve server name to an IP address.
Connecting to update2.vendetta-online.com:21024...
Welcome to Vendetta Online 1.8.431
Changelog:
*** Vendetta 1.8.431
- Your Home Station is now set to the station you're launching from if
Connecting to cloud.patchstorm.com:21024...
getaddrinfo error: Name or service not known
Failed connecting to cloud.patchstorm.com
Unable to resolve server name to an IP address.
Connecting to update2.vendetta-online.com:21024...
Latest version: vendetta-1.8.431
Version is current; verifying files...
Connecting to cloud.patchstorm.com:21024...
getaddrinfo error: Name or service not known
Failed connecting to cloud.patchstorm.com
Unable to resolve server name to an IP address.
Connecting to update2.vendetta-online.com:21024...
Welcome to Vendetta Online 1.8.431
Changelog:
*** Vendetta 1.8.431
- Your Home Station is now set to the station you're launching from if
Update: Tried a different provider, MTN for the internet, and the link is working perfectly, with no problems.
Connecting to cloud.patchstorm.com:21024...
Latest version: vendetta-1.8.431
Version is current; verifying files...
Connecting to cloud.patchstorm.com:21024...
Welcome to Vendetta Online 1.8.431
Changelog:
*** Vendetta 1.8.431
- Your Home Station is now set to the station you're launching from if
you'r of newly opened menus.
-------------------------------------------
Went back to my usual provider, and the connection error came back. Somewhere between my connection and the cloudserver, there is a problem.
Connecting to cloud.patchstorm.com:21024...
Latest version: vendetta-1.8.431
Version is current; verifying files...
Connecting to cloud.patchstorm.com:21024...
Welcome to Vendetta Online 1.8.431
Changelog:
*** Vendetta 1.8.431
- Your Home Station is now set to the station you're launching from if
you'r of newly opened menus.
-------------------------------------------
Went back to my usual provider, and the connection error came back. Somewhere between my connection and the cloudserver, there is a problem.
Yoda: Interesting, I wasn't able to test his servers, as they refused recursion for my address space. I assumed they were locked to only the provider's address space.
Dilan: Have you tried replacing your ISP-provided nameservers with 8.8.8.8? It's worth a shot. There may be some unusual DNS proxy done for Vodacom's internal network (AT&T does things like this, on their cell network). Transparent proxies can sometimes "transparently" break things, but it might be configured only to grab their own DNS queries, and not those to other servers.
Dilan: Have you tried replacing your ISP-provided nameservers with 8.8.8.8? It's worth a shot. There may be some unusual DNS proxy done for Vodacom's internal network (AT&T does things like this, on their cell network). Transparent proxies can sometimes "transparently" break things, but it might be configured only to grab their own DNS queries, and not those to other servers.
@Incarnate. Will do as you suggest.