I built several sites for clients which use Google Storage for their larger media. They have all been running fine since 2010, then in the past few days all of them started getting the 403 errors.
I scanned back through my Google Storage emails, and I don't see any announcements that would be relevant. No files have changed in the client's sites.
Is anyone having a similar issue? What can I do to fix this?
Thanks!
Sorry to have left this hanging. The issue was caused by a credit card expiration date mismatch.
Facepalm.
Thanks for your attention Nikita.
Related
I am unable to access Google Cloud DNS page.
All it shows is:
"DNS API is being enabled. This may take a minute or more."
Then it reloads and repeats showing the same message.
The API is already enabled, and the records I created works. No problem with DNS.
I need to modify records, but I can't because of this problem.
I tried opening the page in different computers and different browsers without addons, same result.
If there is a better place to ask, please do tell.
Thank you.
You should be able to access the page regardless of what computer / browser you're using.
If you cannot it's either a temporary outage which you can check here or a bug.
The only thing to do here is to contact paid support for more immediate help and if the time is something you can afford report this at Google's IssueTracker and get help for free - however it may take a few days. It is possible that only you are affected. Please describe the issue in as much detail as possible - this will expidete the process.
I am working on PayPal integration with omnipay package. Firstly It was working fine but after some time it started to show internal server error. I reached on Google and found this problem is having from last few days. I want to know, how to solve this? is PayPal solved this issue or this issue is having due to any error in my script?
my script
Error page
Finally I got my answer
The issue was I was passing wrong and cancel return URLs. These URLs are of my local server IP. when I removed this and applied a live server details it started again.
I also done some R & D and found PayPal is having this issue from last few months.
Thanks guys for your kind support!
This could be related to the downtime that sandbox has been experiencing over the last 24 hours. The internal teams were able to diagnose the problem and repair it. Can you please check to see if your code is working now? This was limited to sandbox and didn't affect production.
Has anyone encountered this error? It is not giving a description from console.firebase.google.com.
The issue here is likely that you've run out of quota in our free plan. The console will be affected by this, unfortunately :(
You can verify this by performing any request (or looking in the developer console) and seeing a 402 which means you've exceeded your quota. Just upgrade your plan to a paid plan or wait until the quota refreshes (midnight PST).
We're working on a better error message here, since it's obviously not a great experience to see nothing.
Maybe someone knows what the cause of the error? I am trying to come and continue the activation of your NVP / SOAP API Apps, but the server responds with an error. Someone knows what's going on?enter image description here
UPDATE: It looks like over the weekend the app services went back online, so all should be fixed now. Let me know if you encounter any issues with it, and definitely very sorry for any issues this downtime caused you.
At the moment there are some issues at paypal-apps.com, which is affecting the site and ability to create new applications. The teams are working on the servers that are affected and will hopefully have more information soon. I'll update as soon as I have more details though.
I have my script email me when there is a problem creating a recurring transaction with authorize.net. I received the following at 5:23AM Pacific time:
SOAP-ERROR: Parsing
WSDL: Couldn't load from 'https://api.authorize.net/soap/v1/service.asmx?wsdl' :
failed to load external entity "https://api.authorize.net/soap/v1/service.asmx?wsdl"
And of course, when I did exactly the same thing that the user did, it worked fine for me.
Does this mean authorize.net's API is down? Their knowledge base simply sucks and provides no information whatsoever about this problem. I've contacted the company, but I'm not holding my breath for a response. Google reveals nothing. Looking through their code, nothing stands out. Maybe an authentication error?
Has anyone seen an error like this before? What causes this?
Maybe as a back up you can cache the WSDL file locally and in case of network issues use the local copy. I doubt it changes often so if you refresh it weekly that should be satisfactory as the file will probably not be stale by then.