MM crash reporting fails - HTTP error 301

[ggibby]

After installing KB4577063 2020-09 Cumulative Update Preview
and restarting,
MediaMonkey launches from a Startup folder shortcut,
then freezes, and the reporting window opens.

I fill out the box and click Send, then:

"HTTP error code: 301 (moved permanently)"
Followed by:
"Sorry, sending the message didn't work."

MM then continues opening normally.
Repeatable twice so far.
I Snipped the report screens, don't know how valuable those are.

[Lowlander]

Have you tried reinstalling the latest release: https://www.mediamonkey.com/forum/viewt ... =8811&sd=d

[ggibby]

That is the version I am running, will reinstall.

Notable that I am having problems with the current Discogs Batch Tagger script
(already in communication with dev)
and uninstalling that cleared the freeze problem.

[Lowlander]

Oh, then it doesn't seem like a MediaMonkey problem.

[ggibby]

Well, the freeze isn't (sort of), but the reporting failure is notable.

Is there a way to force an error report to check that HTTP error?

[Lowlander]

step 4b: https://www.mediamonkey.com/forum/viewt ... p?f=7&t=69