Jump to content

SITE UPGRADE WARNING


S4GRU

Recommended Posts

My latest comm's with Chris of Tapatalk tech support:

 

Hi David,   The forum appears to be not functioning correctly this evening, I'll try tomorrow. Sorry for the wait!   Chris Tapatalk Support

Translation: it doesn't work in Tapatalk, so the forum must not be working right. LOL. Or he immediately got blocked thanks to their crappy code. Oh that would be precious.. [emoji48]

 

  • Haha 1
Link to comment
Share on other sites

Latest from my conversation:

 
 
Hi David, 
I think we figured out what might be the problem here. 
The forum admin updated their forum system to 4.3 but has an older version of Tapatalk plugin installed. 
We have contacted the forum admin to update their Tapatalk plugin. Please do the same as requests from members are attended to more quickly. 
 
Regards, 
Tapatalk Support Team
 
(I'm just the messenger) ?
 

 

Link to comment
Share on other sites

Bitten again by bug last night. First time in a while.

Sent from my LG-LS997 using Tapatalk

Link to comment
Share on other sites

9 hours ago, davidtm said:

Latest from my conversation:

 
 
Hi David, 
I think we figured out what might be the problem here. 
The forum admin updated their forum system to 4.3 but has an older version of Tapatalk plugin installed. 
We have contacted the forum admin to update their Tapatalk plugin. Please do the same as requests from members are attended to more quickly. 
 
Regards, 
Tapatalk Support Team
 
(I'm just the messenger) ?
 

 

They did drop a new plugin on Friday.  I just installed it now.  Let me know how it goes!

Robert

  • Like 1
Link to comment
Share on other sites

  • 4 weeks later...

403 ERROR

The request could not be satisfied.


Request blocked.


Generated by cloudfront (CloudFront)
Request ID: wYxrleriwRlmP1lDOPidiN7fPDGPZrhCRs45IwxJlrPTZu2FgzIEbg==

 

Error still happening when I have issues that allow my phone with tapatalk (latest version) to be the same Natted IP as PC. (Firefox browser (latest).

Link to comment
Share on other sites

  • 2 weeks later...
My Fios IP is blocked again. Consistently happens when I use Tapatalk to browse the board.. if I stay logged in for notifications but use the mobile website, it doesn't seem to happen.
-Mike
"Chris" at Tapatalk asked me for blocked IPs vs not blocked IPs the last time I had an exchange with him. You might send him your issue backed up with IP addresses.


Sent from my Pixel 2 using Tapatalk

Link to comment
Share on other sites

  • 6 months later...

I haven't been blocked for a long time now. Seems that problem is fixed.

But it takes foreeeeeverrrrr for Tapatalk to update it's cache from S4GRU when launching the app and opening the site. Anyone else see this?

... I can help get it going a bit faster if I force close the app and clear it's cache before launching.

Sent from my Pixel 2 using Tapatalk

  • Like 1
Link to comment
Share on other sites

I haven't been blocked for a long time now. Seems that problem is fixed.

 

But it takes foreeeeeverrrrr for Tapatalk to update it's cache from S4GRU when launching the app and opening the site. Anyone else see this?

 

... I can help get it going a bit faster if I force close the app and clear it's cache before launching.

 

Sent from my Pixel 2 using Tapatalk

 

 

This is by far the slowest loading forum I have in Tapatalk, though XDA isn't far behind. Sometimes the topics list won't load at all for me. I've never tried clearing the app cache. Posting seems normal though.

 

Link to comment
Share on other sites

I just checked to see if they have released a new plug-in to see if it would help performance.  But they are still on version 1.5.2.  Which we upgraded S4GRU to back in May.

Robert

 

EDIT:  I reinstalled them to see if that helps.

  • Like 3
Link to comment
Share on other sites

I haven't been blocked for a long time now. Seems that problem is fixed.

But it takes foreeeeeverrrrr for Tapatalk to update it's cache from S4GRU when launching the app and opening the site. Anyone else see this?

... I can help get it going a bit faster if I force close the app and clear it's cache before launching.

Sent from my Pixel 2 using Tapatalk


I have the same issue with it often not loading in Tapatalk. I've found that I can just swipe away Tapatalk and reopen it, and then it works quickly.

Sent from my Pixel 3 XL using Tapatalk

  • Like 2
Link to comment
Share on other sites

  • 1 month later...

On another note, the site in general has seemed to have issues the past several days in terms of either accessibility or latency from my end.  Hadn't seen any particular posts from others expressing the same thing but I've experienced it both at work, at home and on via mobile.

Having said the above, right now and generally today so far its been fine.

  • Like 4
Link to comment
Share on other sites

I PM'd Robert a few days ago....    I have a very difficult time loading the site and selecting the threads.     It's been about 5 or 6 days.    Did anyone notice either Tuesday or Wednesday the site was completely down in the morning (7-8am eastern time)?  I was hoping it would be fixed by now..,. but am still having issues. 

Link to comment
Share on other sites

I reached out to Robert a few days ago regarding error messages and timeouts when trying to load certain threads over the last week, and slow loading times on others. He said there was a software update available that he was going to try. Perhaps that did the trick, as everything seems to be working great today.

-Mike

Link to comment
Share on other sites

3 hours ago, PythonFanPA said:

On another note, the site in general has seemed to have issues the past several days in terms of either accessibility or latency from my end.  Hadn't seen any particular posts from others expressing the same thing but I've experienced it both at work, at home and on via mobile.

Having said the above, right now and generally today so far its been fine.

I also have been having issues with the site in the past few days.

Link to comment
Share on other sites

Clinking on a existing thread to see  a new comment is sometimes slow.  Might take 10 seconds to get a response. Might even have to click on the new comment the second time. This is the only site I have with this issue.  This issue started for me over a week ago.

  • Like 2
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...