SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

Submitting pair to MB - Error 301

Is anyone else getting this error:

“There was a problem submitting to the musicbrainz server, failing with http response code 301 and error”?

It’s been happening for about a week now whenever I try to upload the MB/PUID pair. This doesn’t change depending on which buttons/menus I use.

The separate fingerprinter app seems to still be working, but there isn’t exactly any useful feedback.

Yes I am getting the same error

Are we talking about Submit Musicbrainz/PUID Pair or Submit Musicbrainz/AcoustId (the 2nd one is the new task that works similar to the standalone fingerprinter), Im not getting error 301’s in either case.

The MB/PUID pair. The meter (progress bar) dialog shows up and starts scanning, but then the error quickly shows up with the message above.

This didn’t change with a release either. I believe it happened in 4.0.0 final. It was working just fine, then it errored without anything changing. I figured MB was doing maintenance or something, but now it’s been happening for a couple weeks, so I asked here.

Can you send me your support files then because I cannot repllcate this problem.

Sent

Paul

I can’t add new releases into Musicbrainz it brings back a blank add release form. would this be connected to the error 301 which I still when trying to submit anything

Hmm, I don’t get either error are you sure you dont have a firewall issue ?

BTW djotley, do you live in Otley, I was there last week.

Paul

I will give that a check although don’t think anything should have changed since it last worked. But you never know

No I live in Beverley East Yorkshire

Paul

I have sorted it

The URL for Musicbrainz submissions was going to the old site I have now changed to point to http://musicbrainz.org and is now working perfectly

[quote=djotley]Paul

I have sorted it

The URL for Musicbrainz submissions was going to the old site I have now changed to point to http://musicbrainz.org and is now working perfectly[/quote]

This did it for me too. I didn’t even notice that it (the URL) changed back. Thanks.

Probably my fault, not making this clearer to those who tried the beta.