what should I do about this? Help please
anyone getting the 503 error certeficate?
@darkthunder said:
what should I do about this? Help please
Who do we tag?
eh I think some staff members. I think I saw some of em on bug reporting before. Hopefully they're active
It's probably caused by a influx of information related to the cache of the website. A large influx of information at once can cause something like that to occur.
I've been getting this for days now. It works fine for a while, then the error comes up. Then it works fine again
@darkthunder: only know mods unfortunately. Also, the staff member u tagged hasn't been active on this site for 2years... maybe u can pm mod & ask them for an active staff?
For me, the errors happened twice today; 10h ago & 4h ago, barely a day's issue.
@darkthunder: only know mods unfortunately. Also, the staff member u tagged hasn't been active on this site for 2years... maybe u can pm mod & ask them for an active staff?
For me, the errors happened twice today; 10h ago & 4h ago, barely a day's issue.
yeah I'll try asking the mods
@juiceboks@owie@jedixman@vance_astro do you guys know any active staff member?
is @wcarle active?
maybe @inferiorego
wcarle hasn't been active for a year and inferiorego hasn't been on for the past 4 months. U can check this out my clicking the persons profile then click on forums under their name
wcarle hasn't been active for a year and inferiorego hasn't been on for the past 4 months. U can check this out my clicking the persons profile then click on forums under their name
yes I saw, but I think there might be a slight chance they'll see this cuz its not been that long since they were inactive
Yeah, I have. Been getting 503 Errors every 10 minutes or when I click on a thread. It's really annoying.
Yeah, I have. Been getting 503 Errors every 10 minutes or when I click on a thread. It's really annoying.
ikr.
This is where you submit technical questions to Support:
I have used it for a variety of things in the past fairly successfully.
I have personally found that switching browsers worked fine with this error, and then eventually came back to the original browser and it was OK again.
But yes, someone should go ahead and submit a bug report.
Maybe is there something wrong with the site's code? Because it's not only one or two users with this problem, but a huge majority of the users have this bug.
This is happening pretty consistently for me contacting the API with python. Basically, it is unusable.
It is curious that they did get new certs in February and the issuing intermediate CA seems to be a relatively new Digi instance. I'm thinking that Fastly needs to update a ca-bundle somewhere.
Its a captain-less ship. I guess just enjoy the fact that it was free and fun when it was functional and the original creators gave a sh!t about the site.
This error occurs when a certificate installed at the origin expires. To resolve this, renew your certificate or download a new one.
Regards,
James (QuickBooks Hosting Expert)
Please Log In to post.
Log in to comment