SlideShowPro Account Center: User Forums

bdaily,

Thanks for the response.  The test fails on the third step with the same blank cURL error as the activation page. This is on a dedicated Rackspace server with our own dedicated firewall which we have full control of.

From shell, I can resolve the correct IP address for slideshowpro.net--but I can't ping it or connect in any other way.  I even put a ANY to ANY rule for your server's IP address, but still have the same problem.

Rackspace is able to ping your server from the datacenter without issue--only our server is affected.  They are not doing any type of outbound blocking, so that puts that angle to rest.

Doing a traceroute shows that we're not able to ping past the last "net2ez" hop, so I'm assuming that our IP address is being blocked by your host, MediaTemple.  Here's my traceroute from our server:

[root@s93511 ~]# traceroute slideshowpro.net
traceroute to slideshowpro.net (72.47.194.27), 30 hops max, 38 byte packets
1  72.3.138.194 (72.3.138.194)  0.592 ms  0.749 ms  0.722 ms
2  core3-121.dfw1.rackspace.net (72.3.129.132)  0.380 ms  0.356 ms  0.360 ms
3  vlan903.edge3.dfw1.rackspace.com (72.3.128.51)  2.694 ms  1.933 ms  1.919 ms
4  xe-8-1.r02.dllstx09.us.bb.gin.ntt.net (157.238.225.221)  1.974 ms  2.066 ms  2.344 ms
5  4.68.63.221 (4.68.63.221)  1.488 ms te-10-1-0.edge2.Dallas3.level3.net (4.68.63.225)  1.590 ms 4.68.63.221 (4.68.63.221)  1.517 ms
6  vlan79.csw2.Dallas1.Level3.net (4.68.19.126)  6.611 ms vlan89.csw3.Dallas1.Level3.net (4.68.19.190)  8.502 ms vlan79.csw2.Dallas1.Level3.net (4.68.19.126)  8.116 ms
7  ae-93-93.ebr3.Dallas1.Level3.net (4.69.136.165)  14.285 ms ae-63-63.ebr3.Dallas1.Level3.net (4.69.136.153)  14.247 ms ae-93-93.ebr3.Dallas1.Level3.net (4.69.136.165)  2.678 ms
8  ae-3.ebr2.LosAngeles1.Level3.net (4.69.132.77)  37.720 ms  35.813 ms  35.669 ms
9  ae-72-72.csw2.LosAngeles1.Level3.net (4.69.137.22)  37.092 ms  35.944 ms  35.684 ms
10  ge-9-0.ipcolo2.LosAngeles1.Level3.net (4.68.102.43)  35.365 ms  35.621 ms  35.621 ms
11  WBS-CONNECT.ipcolo2.LosAngeles1.Level3.net (4.71.36.202)  36.918 ms  36.710 ms  36.834 ms
12  cr01-2-2.lax4.net2ez.com (64.93.64.74)  36.934 ms  36.961 ms  36.698 ms
13  cust-77.lax4.net2ez.com (64.93.75.14)  37.216 ms  36.763 ms  36.392 ms
14  * * *
--SNIP--
30  * * *

As you can see, we're not able to get past the last hop before the MediaTemple datacenter.

If you need to follow up with them on this, you can get our server's IP by pinging the hostname of my contact e-mail, or by just e-mailing me.

Please let me know if you need additional information from me on this; thanks!

What happened about this? I have the exact same problem but don't know how to traceroute from my dedicated server in toronto to slideshowpro.net

thanks, I'm trying it right now. Its a linux box.

tjyoung,

This looks like it is probably a DNS issue, since it says it can't resolve the hostname.  To check this possibility, you could use the "dig" command to run a DNS query (all we care about are DNS A records):

dig slideshowpro.net A

You should get back something looking like this:

[root@server ~]# dig slideshowpro.net A

; <<>> DiG 9.2.4 <<>> slideshowpro.net A
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38788
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;slideshowpro.net.              IN      A

;; ANSWER SECTION:
slideshowpro.net.       43200   IN      A       72.47.194.27

;; AUTHORITY SECTION:
slideshowpro.net.       172800  IN      NS      ns1.mediatemple.net.
slideshowpro.net.       172800  IN      NS      ns2.mediatemple.net.

;; ADDITIONAL SECTION:
ns1.mediatemple.net.    19      IN      A       64.207.129.18
ns2.mediatemple.net.    19      IN      A       64.207.128.18

;; Query time: 15 msec
;; SERVER: 1.2.3.4#53(1.2.3.4)
;; WHEN: Sat Aug  2 16:14:58 2008
;; MSG SIZE  rcvd: 130

As you can see here, I'm getting an IP address of 72.47.194.27 for the slideshowpro.net server (this would be a "normal" response--if you don't get an A record, then DNS is your problem for sure).

Regardless of the DNS response, you should try to ping the IP address listed above to make sure you can connect when circumventing DNS:

ping -c 5 72.47.194.27

If you're able to access the server directly by IP address, you should receive something like this:

[root@server ~]# ping -c 5 72.47.194.27
PING 72.47.194.27 (72.47.194.27) 56(84) bytes of data.
64 bytes from 72.47.194.27: icmp_seq=0 ttl=52 time=40.9 ms
64 bytes from 72.47.194.27: icmp_seq=1 ttl=52 time=37.1 ms
64 bytes from 72.47.194.27: icmp_seq=2 ttl=52 time=37.0 ms
64 bytes from 72.47.194.27: icmp_seq=3 ttl=52 time=37.0 ms
64 bytes from 72.47.194.27: icmp_seq=4 ttl=52 time=37.7 ms

--- 72.47.194.27 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 37.015/37.996/40.994/1.533 ms, pipe 2

If you're able to ping the IP address, but you're not able to lookup the IP from the hostname, then this is definately a DNS issue.

Got this now: changed some info at my end on server

# traceroute slideshowpro.net
traceroute to slideshowpro.net (72.47.194.27), 30 hops max, 40 byte packets
1  216.126.64.225 (216.126.64.225)  0.747 ms  0.708 ms  0.700 ms
2  24.244.216.21 (24.244.216.21)  0.647 ms  0.632 ms  0.625 ms
3  gi9-21.mpd01.yyz02.atlas.cogentco.com (38.101.48.69)  1.048 ms  1.526 ms  1.512 ms
4  te8-2.mpd01.ord01.atlas.cogentco.com (154.54.7.73)  15.972 ms  15.961 ms te3-3.mpd01.ord01.atlas.cogentco.com (154.54.2.161)  16.428 ms
5  vl3490.mpd01.ord03.atlas.cogentco.com (154.54.6.206)  16.416 ms  16.402 ms  16.861 ms
6  btn.ord03.atlas.cogentco.com (154.54.10.58)  16.367 ms  16.291 ms  16.276 ms
7  avanz.ge3-1.2.cr01.lax03.pccwbtn.net (63.218.91.30)  78.208 ms  78.195 ms  78.665 ms
8  cr01-2-2.lax4.net2ez.com (64.93.64.74)  77.645 ms  78.310 ms  78.274 ms
9  cust-77.lax4.net2ez.com (64.93.75.14)  78.269 ms  78.271 ms  78.263 ms
10  mt-aces-02-01.mediatemple.net (72.10.63.246)  78.271 ms  78.241 ms  78.236 ms
11  vz132.mediatemple.net (72.47.194.3)  78.674 ms  79.160 ms  77.692 ms
12  slideshowpro.net (72.47.194.27)  78.178 ms  78.159 ms  78.132 ms

Ping also works:

ping -c 5 72.47.194.27
PING 72.47.194.27 (72.47.194.27) 56(84) bytes of data.
64 bytes from 72.47.194.27: icmp_seq=1 ttl=54 time=78.4 ms
64 bytes from 72.47.194.27: icmp_seq=2 ttl=54 time=78.3 ms
64 bytes from 72.47.194.27: icmp_seq=3 ttl=54 time=78.2 ms
64 bytes from 72.47.194.27: icmp_seq=4 ttl=54 time=78.6 ms
64 bytes from 72.47.194.27: icmp_seq=5 ttl=54 time=78.0 ms

--- 72.47.194.27 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 78.025/78.353/78.656/0.411 ms

OMG Its finally working!!!!!!!
I don't have a clue what actually worked I did so many things, it may have been a simple apache restart after my firewall changes perhaps?

Anyways, thanks a million Harvestonline. You really helped.

todd