Jump to content
Dante Unbound: Known Issues ×
Dante Unbound: Share Bug Reports and Feedback Here! ×

Login Failed? Here Is A Quick Way To Self Diagnose And Solve!


[DE]Rebecca
 Share

Recommended Posts

Hey I'm on...here is what I've done.

 

1) Open Internet Explorer as an Admin.

 

2) Hold alt and left click.

 

3) Clear the SSL Cache in the Content tab

 

4) Go to that place where we had the Root Thawte system

 

5) Delete them - Running IE as an admin allows this.

 

6) Go back to Warframe.com main page and reinstall the certificates.

 

It worked~

1365773365503.jpg

Link to comment
Share on other sites

Hey, be fair. It is in beta, bugs happen. 

 

Just wish this one hadn't happened to me on my weekend off ;_;

Be fair of what? Same bug happened in Update 6, same bug happened in Update 7. This is not FAIR. This is disrespect of us - players who support DE with our money.

Edited by Armanello
Link to comment
Share on other sites

Be fair of what? Same bug happened in Update 6, same bug happened in Update 7. This is not FAIR. This is disrespect of us - players who support DE with our money.

And it's probably a different issue causing it each time, since each instance appears to be affecting a different group of people. That's why the game is in BETA. DE is not trying to screw you over, or disrespect you. They're doing the best they can to put out a fun product that works, but that's why it's not officially "done" yet. It still has big kinks to work out.

Link to comment
Share on other sites

Add all launchers to firewall exceptions.

When I say disabled i mean it's no longer even running. I used msconfig to stop it from even starting. Running in a clean boot state.

My computer is also running in my routers DMZ. I know the risks and for testing it's fine.

 

 

For some reason I still had the issue. This solution worked for me: 

Solution for NOD32 
NOD32 - Advanced Settings - Filtering Protocols - Applications excluded
Enable access to the "Launcher.exe" and "Warframe.x64.exe" to avoid problems.
 
Now I am playing without problems
Edited by cactuarknight
Link to comment
Share on other sites

 

When I say disabled i mean it's no longer even running. I used msconfig to stop it from even starting. Running in a clean boot state.

My computer is also running in my routers DMZ. I know the risks and for testing it's fine.

 

 

For some reason I still had the issue. This solution worked for me: 

Solution for NOD32 
NOD32 - Advanced Settings - Filtering Protocols - Applications excluded
Enable access to the "Launcher.exe" and "Warframe.x64.exe" to avoid problems.
 
Now I am playing without problems

 

That what I talking about.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...