Consistently timing out after 300s when deploying to non-snapshot servers

Central Repository
1

I have seen several existing tickets discussing timeouts on the old servers.

I am using the new s01.oss.sonatype.org server.

I can deploy snapshot artifacts. However, I get a consistent timeout error when trying to deploy non-snapshot artifacts.

The error is always the same. See attached.

Finally, the strange thing is that I can deploy both snapshots and releases to Sonatype on my laptop but not on the build server that sits on the same network as me. Both have GPG keys configured and credentials set in settings.xml. AFAIK, I don’t have any extra timeout parameters on my laptop and it takes less than 3 minutes to deploy everything anyway.

Thoughts?

Screen Shot 2022-09-08 at 4.36.14 PM
Screen Shot 2022-09-08 at 4.36.14 PM1920×746 154 KB

2

This isn’t the right forum for your question, please see the central documentation.

https://central.sonatype.org/pages/support/

3

Cheers. Moved it to Central Repository.

4

Closing. It was due to not having uploaded my GPG server keys. The strange part that I didn’t get this message until having tried deploying multiple times. There was no error message until the last build and then I got:

build 16-Sep-2022 10:26:18 [ERROR] Rule signature-staging failures
build 16-Sep-2022 10:26:18 [ERROR] * No public key: Key with id: (bcdc32d13dc9393) was not able to be located on <a href=http://keyserver.ubuntu.com:11371/>http://keyserver.ubuntu.com:11371/</a>. Upload your public key and try the operation again.
build 16-Sep-2022 10:26:18 [ERROR] * No public key: Key with id: (bcdc32d13dc9393) was not able to be located on <a href=https://keys.openpgp.org/>https://keys.openpgp.org/</a>. Upload your public key and try the operation again.
build 16-Sep-2022 10:26:18 [ERROR] * No public key: Key with id: (bcdc32d13dc9393) was not able to be located on <a href=http://pgp.mit.edu:11371/>http://pgp.mit.edu:11371/</a>. Upload your public key and try the operation again.