550 Requested action not taken: internal server error

Asked by Panda Jim

Dput command refused to work and output following error when I uploading to PPA:

<i>i@focal:~$ dput ppa:ubuntuhandbook1/test2 dvdstyler_3.2-0build4~ubuntu20.10_source.changes
Uploading to ppa (via ftp to ppa.launchpad.net):
  Uploading dvdstyler_3.2-0build4~ubuntu20.10.dsc: 550 Requested action not taken: internal server error
Note: This error might indicate a problem with your passive_ftp setting.
Please consult dput.cf(5) for details on this configuration option</i>

It was caused by my network change. I added a missing 'NEWS' file into the package source. However, it caused uploading issues. Google and gmail is blocked in my country, so I connected to VPN to check email, then made change and upload the package again.

The upload got stuck at last 1 KB due to poor network speed. So I stop it, disconnect VPN and re-upload it. Finally I gets into this 550 error after a few times of connecting / disconnecting VPN.

Now even switching to another Ubuntu (I've dual Ubuntu boot) will not upload. Please help.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Panda Jim
Solved:
Last query:
Last reply:
Revision history for this message
Colin Watson (cjwatson) said :
#1

This was an outage at our end, but the outage has been fixed since about 14:45 UTC, and other users have confirmed it to be fixed for them. If you're still seeing this even when you retry after receiving this message, let us know.

Revision history for this message
Panda Jim (ubuntuhandbook1) said :
#2

Thanks, working now by adding --passive flag.

Revision history for this message
Nicolas Palix (npalix) said :
#3

Hi,

Is the outage back ?

The FTP command is woking fine.
It fails to upload after the data port is opened in passive mode.

Revision history for this message
Colin Watson (cjwatson) said :
#4

Probably a different issue related to firewall rules; this came up recently and was supposed to have been fixed but does seem to have reappeared. I've reopened our internal ticket with our sysadmins about this.

Revision history for this message
Nicolas Palix (npalix) said :
#5

From my side, it sounds like the passive port provided by the server is not open.
My client try to connect without success (no reply received).
So the firewall is indeed maybe involved.

NB1: IPv6 is used.

NB2: Same behaviour with dput and dput-ng.

Revision history for this message
Colin Watson (cjwatson) said :
#6

Yes, it looks like it was fixed for IPv4 but not IPv6. I've passed that information on. (I missed this earlier because I had to tether via my phone for reasons, and that only does IPv4 ...)

Revision history for this message
Colin Watson (cjwatson) said :
#7

This should now be fixed for IPv6 too.