Tapatalk issues...

[ConqSoft]

So I did a few tracerts today while I was on my mobile connection and it always stopped at the same point. But even the few hops before that were showing very slow response times.

traceroute to camaro5.com (192.184.8.128) , 5 relative hops max, 52 byte packets
1 255.sub-66-174-168.myvzw.com (66.174.168.255) 363.039 ms 375.438 ms 382.404 ms
2 225.sub-69-83-51.myvzw.com (69.83.51.225) 44.999 ms 58.154 ms *
3 194.sub-69-83-51.myvzw.com (69.83.51.194) 132.573 ms 134.236 ms *
4 228.sub-69-83-32.myvzw.com (69.83.32.228) 127.724 ms 136.331 ms *
5 1.sub-69-83-32.myvzw.com (69.83.32.1) 133.933 ms * *
6 63.122.230.125 (63.122.230.125) 928.033 ms * *
7 0.xe-10-1-0.br3.atl4.alter.net (152.63.84.105) 127.446 ms * *
8 xe-0-5-0-21.r03.atlnga05.us.bb.gin.ntt.net (129.250.9.105) 977.950 ms * *
9 ae-7.r21.dllstx09.us.bb.gin.ntt.net (129.250.3.91) 1765.886 ms * *
10 ae-0.r20.dllstx09.us.bb.gin.ntt.net (129.250.2.58) 1317.845 ms * *
11 * * *
12 ae-1.r05.lsanca03.us.bb.gin.ntt.net (129.250.2.230) 368.491 ms 448.845 ms *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *

Just wondering if that's the same roadblock others are hitting? (There are several free tracert apps for both iOS and Android.)

[OneSickS10]

My last hit was

#14 129.250.5.86 ae-2.r05.lsanca03.us.bb.gin.ntt.net Ping:380.802

I did the same thing from my PC and got the same result. I don't think we are tracing the right route. The problem isn't with Camaro5.com it must be with whatever it uses for the Tapatalk app. How we get that address, is beyond me. I can't find it through the Android Tapatalk app.

I went over to the Tapatalk page and opened a trouble case / bug report. If any other users want to chime in maybe the squeeky wheel will get the grease. Here is the link to the android bug case.
https://github.com/tapatalk/android-issues/issues/201

[Modern07]

I've been having issues with tapatalk but also safari on my iPhone - only with Camaro5 though - all other websites/forums work fine but Camaro5 times out when using tapatalk or safari - very annoying.

Although it is actually working now for the first time in weeks for me!

[ConqSoft]

Tapatalk still communicates through HTTP just like a browser, and like the previous poster said it affects mobile browsing for me as well. So it doesn't appear to be Tapatalk specific.

[911medic]

Originally Posted by ConqSoft

So it doesn't appear to be Tapatalk specific.

It is for me.

[redleader]

Originally Posted by 911medic

It is for me.

and Me
It's at their end: C5 to TT servers

[45thCamaro]

I too am having issues. I believe it is c5. I try using Tapatalk and safari on my iPhone and iPad. No difference if I'm on Verizon's network or wifi. Same results. The web site comes up saying the server stopped responding. I use Tapatalk with other forums and do not have issues.

[ConqSoft]

Originally Posted by redleader

and Me
It's at their end: C5 to TT servers

The TT servers are not involved. The back end pieces for TT are on the C5 servers. It's just an addon that is installed into vBulletin.

The only time TT servers are involved is if you use their service to house your mobile attachments.

I've ran several forums in the past. I'm aware of how TT works.

[OneSickS10]

For all of the Android users. You can try clearing cache and forcing the app to stop, then open it again and see if that resolves it. It didn't work for me but that was one of the suggestions on the support forum.

[Highland Ranger]

Originally Posted by OneSickS10

For all of the Android users. You can try clearing cache and forcing the app to stop, then open it again and see if that resolves it. It didn't work for me but that was one of the suggestions on the support forum.

I'll try it. But I use TT for over a dozen forums I frequent and this only happens with this forum. That tells me its not on my end.

Sent from my Nexus 7 using Tapatalk

[redleader]

I also get the unreadable and nonexistent post pages too:

[The Stig]

Originally Posted by redleader

I also get the unreadable and nonexistent post pages too:
Attachment 649198

It's because Tapatalk updates the app and API's but the Moderators still have the site running on the old code. Heck, the site uses a bulletin version that was published in 2011 and has had 4 major security patches pushed out.

[Drumminxx]

Someone updated the site or did a config change because tapatalk has been working great as of yesterday. I hope it stays this way.

[911medic]

Originally Posted by OneSickS10

For all of the Android users. You can try clearing cache and forcing the app to stop, then open it again and see if that resolves it. It didn't work for me but that was one of the suggestions on the support forum.

I've done this in the past. One time it worked, but only temporarily (and perhaps coincidentally?), the other time it didn't. It's not a solution (for me, anyway).