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
Invalid SSL Certificate
The SSL certificate for https://ufs50.discovery.steamserver.net:8694/ugcupload is invalid and the page will not be loaded (error:-202 status:5).
I tried in order:
- Restart Steam: problem not resolved.
- Clear the Steam web cache: problem not resolved.
- Check for a Steam client update: problem not resolved.
- Activate the Beta version of the Steam client: problem not resolved.
- Check for and update the Steam client: problem not resolved.
Solution that works:
- Google Chrome browser: connect to Steam via the browser, redo the creation publication maneuver to publish the artwork, Google Chrome indicates that the site is not secure, choose to see more options and choose to consult the non-secure site anyway, to see that the publication is validated.
So SSL certificate problem coming from Steam.
Since the Steam client (app) is out of the question, this is an internal issue with Steam's web protocols.
https://steamcommunity.com/groups/SteamClientBeta/discussions/0/599644966903351910/
Yes, that's exactly it, I shared the information with Steam support a few minutes after my message on this topic by creating a Support ticket (taking care to share the link to this topic with them).
In general, when it comes to SSL certificates, it is because it affects the very structure of the web environment, whether it is for a website or for a structure like Steam.
SSL/TSL certificates are essential to "have" a "secure" connection on webservice/website.
However, the rules are changing rapidly in terms of security and certificates are gradually seeing their validity period reduced, forcing websites and structures to focus on automating certificate renewal (when automation is possible) as the renewal cycle accelerates, so much so that by the end of 2027, certificates will be valid for 45 days (whereas a few years ago it was 260 days and more).
No doubt this duration will be further reduced years after 2027...
And if the automation fails or an error occurs, it's a disaster (panic on board).
In short, courage to the webmasters and developers of Steam (Valve).
We will have to be patient, and start getting used to it because this kind of problem is likely to multiply on other platforms other than Steam in the future.
However, be careful, I am not saying anything about the Steam outage, this is just my personal reasoning regarding the problem, I want to be clear about that.
You would think...
https://steamcommunity.com/groups/SteamClientBeta/discussions/0/599645206077305086/