Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Yes it is the correct date and time
For this case, could you please try restarting your computer and Steam client to see if this issue persists? If it does, please follow these steps that may help to resolve this:
1. Press Windows Key + R to bring up "Run"
2. Type "cmd" (without quotes) and hit enter to bring up "Command Prompt"
3. First, type "ipconfig /release" (without quotes) and hit enter.
4. Second, type "ipconfig /renew" (without quotes) and hit enter
5. Lastly, type "ipconfig /flushdns" (without quotes) and hit enter
6. We also advise repairing/reinstalling EAC
7. Restart your computer
This did not work, still getting the error
Pure speculation: I suspect that they've changed something in the way they handle network connections to ensure the connections can't be spoofed. SSL Packet Inspection by any mature firewall serves as a MITM for SSL. If they're looking for "their" SSL cert and they get the firewall cert instead, it could cause this error.
(In other words, if you're on a security-conscious network, you're going to have to drop your pants to play the game.)
I have the game pushing through my firewall already so if that's the problem it should have solved it? What else would I need to do?
Also if they found this problem on the PTB... why would they push it to live without fixing it?
Sadly I am on my universities internet so I cannot white list it. I will have to wait until Behavior fixes it on their end.
Ahh That explains it. I'm on a university network as well.
I've submitted feedback to my firewall vendor (Fortinet) to have this domain scanned and recategorized, which will fix the problem eventually if your universities use their equipment. I don't know what the turnaround time for that would be, and if they're using a different firewall vendor, that will probably require a separate report from a customer.
I will post something to this effect into the BHVR DBD forums as well to see if BHVR can be moved to push the changes on their end to various firewall vendors.