You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I talked to my server provider. He said they were doing all the checks and that there was no problem.
The error repeats itself continuously. For example, it does not work for 3 days and gives this error. It then improves and starts working smoothly. But after an hour or two it breaks down again. It gives this error for 4-5 days every week. But it works for 2 or 3 days.
As far as I can see from other issues I have tried some solutions. I purchased SSL. I bought a new domain and created a new webapi.
But none of this worked. Still can't login to the site.
I'm waiting for your help and solution suggestions.
Gift-Drop.com
The text was updated successfully, but these errors were encountered:
If you have tried the other solutions in the issues section, you should ask your host if curl_exec is disabled; or you can make a php file that will tell you then scroll to the 'disabled functions' area - enabling this fixed it for me: <?php phpinfo(); ?>
Hello,
I have been using Steam Login for 2 years at Gift-Drop. There was no problem until 1 week ago. But now, when the Sign in button is clicked
No OpenID Server found at http://steamcommunity.com/openid gives a error.
I talked to my server provider. He said they were doing all the checks and that there was no problem.
The error repeats itself continuously. For example, it does not work for 3 days and gives this error. It then improves and starts working smoothly. But after an hour or two it breaks down again. It gives this error for 4-5 days every week. But it works for 2 or 3 days.
As far as I can see from other issues I have tried some solutions. I purchased SSL. I bought a new domain and created a new webapi.
But none of this worked. Still can't login to the site.
I'm waiting for your help and solution suggestions.
Gift-Drop.com
The text was updated successfully, but these errors were encountered: