so ive got a custom php script upand running
I followed the cloudfare guide to change NS records to their own and now my login system is experiencing session drops. Members are logged out in a minute or so. I know approximatelly what that is related but didnt find any sufficient answers online or on their discord or community.
This is what ive found so far
https://community.cloudflare.com/t/problem-with-user-session-drop/69671/2
https://community.cloudflare.com/t/session-drop-kick-out-logout-problem/126208/5
and this link which is broken
https://support.cloudflare.com/hc/en-us/sections/200805497-Restoring-Visitor-IPs
Related
I commented this problem on the following thread for an active issue regarding Auth0 lock, but wanted to ask here for more reach in case anyone else has experienced this.
From what I've researched, it seems that many people are having this issue, and it doesn't seem like there's a known explanation to what's going on.
The unfortunate thing is that this is happening to end users, and from what I have seen devs have not been able to reproduce this error.
https://github.com/auth0/lock/issues/1838#issuecomment-918434321
Description
User is able to view our Auth0 Lock
User is not able to successfully sign up
We created an account for them in Auth0 directly and are able to log in using credentials we created for them via the Lock
User is not able to log in using the credentials and is shown the "We're sorry something went wrong when attempting to log in message"
Auth0 logs don't actually show this user's attempts/errors when logging in
Reproduction
Unable to reproduce locally, but trying everything we can to do so, including blocking all cookies (not the problem)
Attempting to get any console warnings from the user as well
Environment
Lock version: 11.30.4
React Version: 17.0.2
Next.js Version: 11.1.0
Chrome 91, Windows
I get 500 Errors when I redirect my users to the OAuth Endpoint from Europe. Has anything changed? It worked for several months
I also don't have the rep yet to comment. But I have been noticing this issue today also.
All of my sites that use Google oauth (different tokens) are returning 500 errors after choosing the google account you want to log in with.
500. That’s an error.
There was an error. Please try again later. That’s all we know.
I checked the status page and I don't see any errors or any other reports of this https://status.cloud.google.com but it seems there is something going on since at least a few of us are seeing this. I have tried from multiple computers on different networks, and I had a friend try on a different google account and had the same issue. I am using the following gem in a rails app:
gem "omniauth-google-oauth2", "~> 0.2.1"
Edit: That page has now been updated with an notice on the bottom.
We are investigating an issue with Authentication services. We will provide more information by 07:30 US/Pacific.
I can't post a comment as a guest but I have been noticing this as well. I have found that several refreshes sometimes bring up the authentication window, but I haven't actually been able to authenticate and connect yet. I am on the Eastern coast of NA trying to access GMAIL api.
This started to happen to me this afternoon , it will occasionally work but most of the time it doesn't.
I have read this may be because you must now past through the oauth_verifier which has only just been changed, although it should not have just yet.
Source GarretMurray - https://twittercommunity.com/t/oauth-access-token-stopped-working-today/1630
He said that after adding the verifier it started to work again !
I also experienced this, but the problem seems to have been resolved by Google. I observed the errors happening on our application from roughly 13:42 - 14:28 UTC.
As per https://status.cloud.google.com/
"We are investigating an issue with Authentication services. We will provide more information by 07:30 US/Pacific."
There is also subsequent post specifically on the Google Cloud App Engine service regarding this outage available at https://status.cloud.google.com/incident/appengine/16003.
Sources: See above.
My question here is pretty simple: how to properly (and 100%) configure both Live Connect and project in Visual Studio 2013 in order for the local application run and authenticate an user properly against Microsoft account.
My question may be simple, but the answer is most likely not as simple. I've been reading countless articles and possible tutorials about this, but they are all fragmented and divided into small parts that do not really conciliate each other.
So below is the situation better described, with the steps I have followed.
[Steps Followed]
1) I have created a simple MVC application using Visual Studio 2013.
2) I have configured the project (using its properties) to use IIS Express with current Project Url : https://localhost:44302/
The project runs quite well, and external authentication with Facebook, Google and Twitter run very well too. Now for the tricky part:
3) I have created account with Microsoft and successfully created application in the Live Connect Developer Center.
4) Since configuring the field Redirect URLs to a simple http://localhost:<port> will not work (well...just because they didn't want it to, I suppose), I have additionally done the following..
5) Mapped in hosts file the following domain to localhost: # 127.0.0.1 mytestdomain.localtest.me
6) Reconfigured in Live Connect the Redirect URLs field to use the newly mapped domain: http://mytestdomain.localtest.me (although I have tried this with or without the port as well).
[End result]
With this configuration, the site runs properly locally. However, when I try to sign in with Microsoft account credentials (so, when I click the "Microsoft" button), I have redirected and received the following message:
"We're unable to complete your request
Microsoft account is experiencing technical problems. Please try again later."
I honestly do not understand why wouldn't this work, when a couple of articles suggested that doing these specific steps would make it work.
What can I be missing, why would this happen at all?
If someone can write here what am I missing and we could all join effort and create in this topic a full fledged, 100% working configuration for local application testing with Microsoft authentication, I believe it would help everyone. If such topic already exist and you can point me to it (because clearly I have missed it) it would also be great.
Thank you in advance,
Mad
Actually I just found out a proper and direct answer to my question. I totally missed it somehow during the last few days of research.
Microsoft's blog has all you need to make it work, and now mine does too. No big explanations and discussions, just basic and direct step by step article.
For those who could not find it and stumbled upon my topic here in StackOverflow, here is the link. Follow it word by word, and it will work.
Answer : Configuring your ASP.NET application for Microsoft OAuth account
This question already has answers here:
Please login to use the PayPal sandbox feature
(5 answers)
Closed 9 years ago.
Since Paypal developer changed in March 2013, I've been unable to get into the sandbox.
I logged in to the new developer site OK with my actual Paypal account details.
I managed to import my accounts into the new development site (marked worryingly as 'beta') using the link
"Looking for Sandbox? Import your test accounts to continue testing. Learn what's new."
But clicking the link 'Sandbox site' on any of the accounts results in me being taken to:
This is the link where I'm greeted with a Paypal Sandbox logo and a single link reading "Please log in to use the PayPal Sandbox features."
Clicking on this link takes you back to where you have come from - that is the developer page where I am already logged in.
I did raise a support question with Paypal, but a week has passed and it's gone unanswered, so I'm hoping someone here can tell me what I'm missing in this new version?
I'm unable to reproduce this. I'm logging into my sandbox accounts just fine. I'm also able to test things like Express Checkout without any issue.
I know that browser cache and cookies can often be a big issue on the sandbox. For example, when I first attempted to try this after seeing your post I was getting a Proxy Error when trying to load sandbox.paypal.com. I closed and re-opened my browser, though, and then everything worked as expected. Maybe give that a shot.
As Andrew Angell points out - this crazy behaviour was down to the web browser caching. I just cleared out everything in Chrome (Tools > Clear Browsing Data) and wiped everything since the beginning of time and that's got it. Nice catch, thanks Andrew. Appreciated.
The reason every browser I tried did this, is because I've used them all with Paypal - of course - so hence they all do the same thing, leading you to thing the issue is upstream.
Clear your cache and cookie simply by pressing
CTRL + SHIFT + DELETE for WINDOWS
COMMAND + SHIFT + DELETE for MAC
It works for me.
Clearing doesn't help me with this, USE CHROME INCOGNITO MODE(new window) - it works for me :)
lately my facebook account got disabled as a 'bad app developer' without any warning. The thing is all of the apps, where I was listed as an admin got disabled, even though they didn't have any negative feedback. Some applications, where my collegues were listed as admins can be restored from their accounts (and they got enabled as they are working correctly). But there is one, where only I was listed as admin, and I can't find a way to send an appeal. There is a notice about a transfer process in the mail I received saying
For more information on recovering or transferring these applications, please visit our FAQ page: http://www.facebook.com/help?faq=17556
But the FAQ page says it can't be found.
Please can somebody point to a tutorial or step-by-step guide how to transfer the app to another account, so I can get enabled again.
Thanks many times.
As far as I am aware there is no way to recover/transfer the app to another account. All you can really do is set up a new app and point it to the same web address. That being said your account was disabled for a reason, so I would read up on the terms and conditions to find out exactly what you did wrong.