OzSTOC

Website Info => Website Problems => Topic started by: Pezzz on January 29, 2014, 10:51:51 AM

Title: Android problem ???
Post by: Pezzz on January 29, 2014, 10:51:51 AM
I originally thought it was just tapatalk, but as i have posted in the tapatalk thread i have since found out that trying to login to the site from any of my android devices gives me an internal server error.
Have tried native Browser, Chrome, Dolphin Browser, and Firefox. Used wireless and 3G.
Works fine on PC using Chrome, Firefox, and IE but all Android fails.
 :CB--
I know double post from tapatalk section but this is now the correct place for this as it is not just tapatalk.
Screenshot from phone attached.
 :wht11 Pezzz
Title: Re: Android problem ???
Post by: Biggles on January 29, 2014, 11:09:32 AM
Waiting for the deluge of Apple "told you so's".        :popcorn
Title: Re: Android problem ???
Post by: Cerebral Knievel on January 29, 2014, 11:20:28 AM
This happened to me last night at work whilst checking the forum on the Note III.
Don't have Tapatalk & use chrome on the phone.
I just refreshed the page & it was OK  :grin
Title: Re: Android problem ???
Post by: Pezzz on January 29, 2014, 11:26:07 AM
This happened to me last night at work whilst checking the forum on the Note III.
Don't have Tapatalk & use chrome on the phone.
I just refreshed the page & it was OK  :grin
I had never logged in before using a browser on android gear and it errored out when i put in user/pass the first time and then onwards when i went to the forum page.
Just charging up a windows phone to test on there and then will try and find old iPhone i have laying around (i think holding a door open) to try on there.

Waiting for the deluge of Apple "told you so's".        :popcorn
I know .....   :fp

 :wht11 Pezzz
Title: Re: Android problem ???
Post by: Brock on January 29, 2014, 01:51:10 PM
Sounds like your phone cant find the right address. maybe the site was down, or the dns server your phone was using couldnt find the right IP.
Title: Re: Android problem ???
Post by: alans1100 on January 29, 2014, 02:33:21 PM
After trying my Galaxy 10.1 tab earlier I had the same issue as posted in the link.

http://ozstoc.com/index.php?topic=5265.msg69834#msg69834 (http://ozstoc.com/index.php?topic=5265.msg69834#msg69834)

I have just tried to access our site (it's booked marked) and it came straight on without a hassle. Temporary glitch maybe?????
Title: Re: Android problem ???
Post by: Brock on January 29, 2014, 02:43:12 PM
I just had the problem using the company wifi, but am in using 3G (Optus)
Title: Re: Android problem ???
Post by: Pezzz on January 29, 2014, 03:56:56 PM
 o:)
Sounds like your phone cant find the right address. maybe the site was down, or the dns server your phone was using couldnt find the right IP.
Not a DNS issue. As I said I tried using wifi which uses my own DNS server which forwards unknown traffic to ISP DNS to still keep Akamai location. Then I tried using 3G (DrOptus). Still no luck.
Seems to be working on Chrome on phone now on a different wireless network. Still using same ISP.
 :||||  :CB--
Title: Re: Android problem ???
Post by: Brock on January 29, 2014, 08:34:56 PM
Might be getting somewhere,

using opera, I can get  an error "500 internal error"

The navigation (address bar is showing

ozstoc.co/mobiquo/smartbanner/ads.php?refer=http%3A%2F%2...... and so on.

Googling seems to indicate it belongs to tapatalk, so as this function is broken at the moment, and android devices seem to look for it with their web browsers, or at least open the link.

I just closed the page and tried again and it opens.  Maybe this will be of helpto Diesel in fixing the page.

Having multiple browsers around seems to be a good idea when looking into problems.
Title: Re: Android problem ???
Post by: Pezzz on January 29, 2014, 09:17:55 PM
Seems to be working for now on Chrome on my phone. Back at home now and still ok.
Haven't bothered with stock browser. Will try that on tablet later tonight.
Title: Re: Android problem ???
Post by: Cerebral Knievel on February 01, 2014, 08:09:31 PM
On reflection, i think at the time i experienced the same problem the phone may have been trying
to connect to the Wi-Fi at work.
I don't foresee this being an ongoing problem.
I expect to have my services terminated upon starting my next rostered shift.
So we can chalk up 2 positive outcomes in the immediate future  :grin