Jump to content

Internal server error

Kaixor

By Kaixor
in General Topics

 Share

Recommended Posts

mikejeep Member Level: LTE Advanced

mikejeep

Posted
Posted

I have noticed that the site briefly goes down shortly after 1:00am Eastern Time quite often.  Initially, s4gru.com is completely unreachable, then it comes back online with the Internal Server Error message you posted, then it goes back live.  Usually only happens for a few minutes, and I can't say that I've seen it consistently every night.  Definitely saw it tonight.  Go pour another beverage of your choice, come back, and by then it's back again.  :)

 

-Mike

Link to comment
Share on other sites
MacinJosh Member Level: LTE Advanced

MacinJosh

Posted
Posted

I've had it happen during the day at both peak and non peak usage times. Strange when it happens. Only lasts for a few minutes, no more than 5 when it does.

 

 

Sent from Josh's iPhone 5 using Tapatalk 2

Link to comment
Share on other sites
doomstang Member Level: 3G EVDO

doomstang

Posted
Posted

I have noticed that the site briefly goes down shortly after 1:00am Eastern Time quite often.  Initially, s4gru.com is completely unreachable, then it comes back online with the Internal Server Error message you posted, then it goes back live.  Usually only happens for a few minutes, and I can't say that I've seen it consistently every night.  Definitely saw it tonight.  Go pour another beverage of your choice, come back, and by then it's back again.  :)

 

-Mike

 

I've noticed this too.  I get home from work at about 11:30pm central and I browse the forums quite often during that time.  It isn't every night but it is fairly often that I get that error and the site is offline for a short time.

When that happens it usually helps persuade me to go to sleep....so maybe it's not so bad after all lol.

Link to comment
Share on other sites
Dkoellerwx Member Level: LTE Advanced

Dkoellerwx

Posted
Posted

It only happens to me a once or twice per month for a few minutes.

 

 

Robert

For a time I saw this happen consistently every night sometime between 11:45pm and 12:15am central. It would only last a few minutes. I haven't been on as much lately to notice if it's still happening, but definitely saw it tonight.

 

Sent from my HTC ONE

 

 

Link to comment
Share on other sites
S4GRU Member Level: LTE Advanced

S4GRU

Posted
Posted

It's routine work that IP Board does with their servers. They choose off times and it's down for a few minutes when it occurs.

 

Robert via Nexus 7 using Tapatalk 4 Beta

 

 

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • mikejeep
      SignalCheck Beta Crew Forum

      By mikejeep · Posted

      It is an Android bug that was reportedly fixed in August 2023 but definitely has not been. I have implemented numerous workarounds in SCP to correct the NR bands the app displays. The OS ignores the possibility that many NR-ARFCNs are valid across multiple bands.. it reports the lowest NR band that is valid for the current ARFCN. In your example, channel 432530 can be n1, n65, or n66.. so the OS just (lazily) reports n1.   Awesome, thanks! I will add an n65 override also.
    • mdob07
      SignalCheck Beta Crew Forum

      By mdob07 · Posted

      Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
    • CalebM
      SignalCheck Beta Crew Forum

      By CalebM · Posted

      Interesting, I saw this too on my AT&T S22 while roaming on US Cellular. I thought it was an Android bug since CellMapper was doing the same thing (didn't get a screenshot of that one). N66 makes more sense than N1. 
    • mikejeep
      SignalCheck Beta Crew Forum

      By mikejeep · Posted

      Thanks, that was good timing, I did see your report as I was buttoning up this latest update and added an override for that.. did it not work?   Ok, was that on AT&T also? Please send a report if you happen to see it again and safely have the opportunity. You can always do the long-press on the fly and then send a later one with an explanation pointing to the earlier one.. your username is attached to the long-press reports, so it's not an issue.
    • mdob07
      SignalCheck Beta Crew Forum

      By mdob07 · Posted

      I sent a report in earlier, n66 reporting as n1. There should be two different reports, I couldn't find the button the first time so I just long pressed the connection type to send, then I remembered where it was. I put a note about the issue on the 2nd report. Both reports from me are for the same issue. Also, it might have been on a prior release but earlier this week I also saw n66 reported as n65 on the app. I was driving and wasn't able to send a report in for that one. 

  • Recently Browsing

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