Page 1 of 1
Magelo timing out?
Posted: Mon Mar 29, 2010 1:25 pm
by Ydiss
Is Magelo timing out for anyone else?
Since yesterday, on two different PCs and two different locations, it won't load at all.
Re: Magelo timing out?
Posted: Mon Mar 29, 2010 1:31 pm
by Lillu
hmm, seems perfectly fine on my end on 3 different hosts. anyone else can confirm this?
Re: Magelo timing out?
Posted: Mon Mar 29, 2010 1:57 pm
by thaylin
Happened to one of my chars (Talra) while on line and looking him up, but not to the other 3 that were on line at the time. Only noticeable thing I saw was his name in the search box brings up 3 possible matches. I had to actually copy the link and then do a reload on the page to get it to load his profile. I am also using Opera as my browser.
Re: Magelo timing out?
Posted: Mon Mar 29, 2010 6:05 pm
by aabamzen
I'm timing out reaching magelo.thehiddenforest.org also.
Re: Magelo timing out?
Posted: Tue Mar 30, 2010 12:49 am
by Ydiss
My friend can't access it either; we both use Google Chrome.
Testing the nasty IE to see if it's that.
Edit: Yup, Magelo works fine in IE... But suddenly doesn't work in Chrome. It used to work fine, though (until the recent issue with the forum host).
Re: Magelo timing out?
Posted: Tue Mar 30, 2010 7:55 am
by Lillu
ok, well magelo url forward and setting were never changed recently, it's the same as before the forum issue.
actually, even the forum CNAME settings are the same now.
Try to delete your browser cache and make an ipconfig /flushdns in cmd.
Re: Magelo timing out?
Posted: Thu Apr 01, 2010 11:58 am
by Ydiss
Works OK now.
Re: Magelo timing out?
Posted: Fri Apr 02, 2010 2:51 am
by Topsy
bah, forum host simply hosts the forums. I would never do anything malicious!
Re: Magelo timing out?
Posted: Sat Apr 03, 2010 7:15 pm
by Ydiss
Topsy wrote:bah, forum host simply hosts the forums. I would never do anything malicious!
Don't think anyone suggested you did?
By the way, it started working with no intervention from me so it must have just been a general and temporary conflict with Chrome. No clue what was causing it but it was clearly not the website or the host itself.