GimpChat down

[Rod]

Code:

General Error
SQL ERROR [ mysql4 ]

Out of range value for column 'wwh_id' at row 1 [167]

An SQL error occurred while fetching this page. Please contact the Board Administrator if this problem persists.

 I get this error trying to load the website. Anyone have any idea what that error means?

[MrsP-from-C]

The database has a wrong value in one of its columns.

Something Omega has to look into ... or his hosting provider

[PixLab]

GC is working fine for me.

[Ofnuts]

(11-25-2024, 08:33 AM)PixLab Wrote: GC is working fine for me.

Not for me....

[CtrlAltDel]

(11-25-2024, 06:59 AM)Rod Wrote:  I get this error trying to load the website. Anyone have any idea what that error means?

Same here:

[MrsP-from-C]

(11-25-2024, 08:33 AM)PixLab Wrote: GC is working fine for me.

Still down for me.

[PixLab]

Seriously... not working for you? Um... strange, could it be "localized"?, i mean, it's still very fine for me, I don't understand why for you it does not work (I'm GMT +8, and yes I did click in the menu and it works), also on this website it said it's down > https://downforeveryoneorjustme.com/gimpchat.com but it works for me....

EDIT:
I can even post... ➤ http://gimpchat.com/viewtopic.php?f=13&t=21441
An idea just cross my mind, maybe delete all the cookies from gimpchat... I'm on a brand new distro, thus my browser does not have "old" cookies from gimpchat... yet (although I went few times already on it, but might be worth a try)
   

[Wallace]

I'm not seeing any errors and was able to login without issue.

[Ofnuts]

(11-25-2024, 02:27 PM)Wallace Wrote: I'm not seeing any errors and was able to login without issue.

Still down for me. As far as I can tell, from my end, GC is 170.249.238.146 and reverse DNS says cp34-ga.privatesystems.net (which is probably the datacenter that hosts it).

[PixLab]

(11-25-2024, 02:27 PM)Wallace Wrote: I'm not seeing any errors and was able to login without issue.

Thanks Wallace to confirm
maybe people need to delete their cookies/site data, not sure it come from "old" cookies or an update from their browser they use, or why not a server update... but it could be worth a try in all case