MySQL Bugs: #117369: ERROR IN CHECK FOR UPDATES

Bug #117369	ERROR IN CHECK FOR UPDATES
Submitted:	3 Feb 6:51	Modified:	3 Feb 7:06
Reporter:	David Thomas	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	8.0.20, 8.0.41	OS:	Windows (Microsoft Windows 10 Pro)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\David.Thomas\AppData\Roaming\MySQL\Workbench\log\wb.log]

Click Check for Updates
Dialog opens:
    Check for updates failed
    <urlopen error unknown url type: https:>;
    Please verify that you Internet connection is available

Internet is fine

Log:
17:38:50 [DB1][      SqlEditor]: Auto saving workspace
17:39:00 [DB1][      SqlEditor]: Auto saving workspace
17:39:10 [DB1][      SqlEditor]: Auto saving workspace
17:39:20 [DB1][      SqlEditor]: Auto saving workspace
17:39:31 [DB1][      SqlEditor]: Auto saving workspace
17:39:41 [DB1][      SqlEditor]: Auto saving workspace
17:39:48 [DB1][ mforms managed]: Adding new timeout
17:39:48 [DB1][ mforms managed]: Creating new TimerHandler
17:39:49 [DB1][ mforms managed]: Showing an error to the user
17:39:49 [DB1][ mforms managed]: Hiding the wait message
17:39:49 [DB1][ mforms managed]: About to show a custom message box
17:39:49 [DB1][ mforms managed]: Creating and showing custom message box
17:39:49 [DB1][ mforms managed]: Running custom message box
17:39:53 [DB1][ mforms managed]: Custom message box closed
17:39:53 [DB1][ mforms managed]: Destructing TimerHandler instance
17:40:01 [DB1][      SqlEditor]: Auto saving workspace
17:40:04 [DB1][ mforms managed]: Adding new timeout
17:40:04 [DB1][ mforms managed]: Creating new TimerHandler
17:40:05 [DB1][ mforms managed]: Showing an error to the user
17:40:05 [DB1][ mforms managed]: Hiding the wait message
17:40:05 [DB1][ mforms managed]: About to show a custom message box
17:40:05 [DB1][ mforms managed]: Creating and showing custom message box
17:40:05 [DB1][ mforms managed]: Running custom message box
17:40:30 [DB1][ mforms managed]: Custom message box closed
17:40:30 [DB1][ mforms managed]: Destructing TimerHandler instance
17:40:31 [DB1][      SqlEditor]: Auto saving workspace
17:40:39 [DB1][ mforms managed]: Opening the URL: http://bugs.mysql.com/report.php?in[status]=Open&in[php_version]=8.0.20&in[os]=7&in[os_det... Windows 10 Pro&in[tags]=WBBugReporter&in[really]=0&in[ldesc]=----[For better reports, please attach the log file after submitting. You can find it in C:\Users\David.Thomas\AppData\Roaming\MySQL\Workbench\log\wb.log]
17:40:41 [DB1][      SqlEditor]: Auto saving workspace
17:40:51 [DB1][      SqlEditor]: Auto saving workspace

How to repeat:
Click Check for Updates

Suggested fix:
no idea

Hello David Thomas,

Thank you for the report and feedback.
This was supposed to be fixed after Bug #110786 but I'm still seeing in WB 8.0.41.

regards,
Umesh

23 Jan 6:40] Umesh Shastry
-- Confirmed that issue still exists, but now we see different error in the pop-up window:

Check for updates failed
<urlopen error unknown url type: https>

Please verify that your internet connection is available.
Allow all to see
View reported bugs
[27 Jan 6:50] Umesh Shastry
On windows:

[Window Title]
MySQL Workbench

[Main Instruction]
Check for updates failed

[Content]
<urlopen error [WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond>

Please verify that your internet connection is available.

[OK]

Getting this on MacOS as well. What I think is happening is the code is asking for http://workbench.mysql.com/current-release

```python
self.json = json.load(urllib.request.urlopen("http://workbench.mysql.com/current-release"))
```

in /Applications/MySQLWorkbench.app/Contents/Resources/plugins/wb_utils_grt.py, line 719.

That URL is then mapped to https://workbench.mysql.com/current-release.

```
$ curl -v http://workbench.mysql.com/current-release
* Host workbench.mysql.com:80 was resolved.
* IPv6: (none)
* IPv4: 104.103.248.35
*   Trying 104.103.248.35:80...
* Connected to workbench.mysql.com (104.103.248.35) port 80
> GET /current-release HTTP/1.1
> Host: workbench.mysql.com
> User-Agent: curl/8.7.1
> Accept: */*
> 
* Request completely sent off
< HTTP/1.1 301 Moved Permanently
< Server: AkamaiGHost
< Content-Length: 0
< Location: https://workbench.mysql.com/current-release
< Date: Fri, 14 Feb 2025 12:52:56 GMT
< Connection: keep-alive
< Server-Timing: cdn-cache; desc=HIT
< Server-Timing: edge; dur=1
< Akamai-Request-BC: [a=95.101.236.183,b=752846103,c=g,n=GB_EN_LONDON,o=20940]
< Akamai-GRN: 0.b7ec655f.1739537576.2cdf8517
< Server-Timing: ak_p; desc="1739537576702_1600515255_752846103_6_3292_19_0_-";dur=1
< 
* Connection #0 to host workbench.mysql.com left intact
```

The `Location:` is the path.

So the code is following the redirect.

If I change the URL in the code to something that does NOT redirect (http://neverssl.com), you get a different error ...

`Unhandled exception: name 'json' is not defined`.

Which is as expected as that site doesn't output anything other than some HTML about why you should use SSL/TLS.

The issue MAY be related to how the OS handles relate paths for loading libraries.

I did some more fiddling and got an error related to that, but I'm not an expert.

Considering the amount of time it took to fix the "isAlive" error, I think we'll all just need to learn to use our browsers to find the updated version, or get Oracle to drop SSL for this endpoint.

It only currently returns ...
```json
{
"fullversion": "8.0.41",
"major": "8",
"minor": "0",
"release": "41"
}
```

Bug #117470 marked as duplicate of this one

Bug #117499 marked as duplicate of this one

Bug #118098 marked as duplicate of this one