Error creating blob: cannot retry due to server authentication, in streaming mode

[jmkgreen]

OK I give up.

[ERROR] Failed to execute goal com.github.github:site-maven-plugin:0.7:site (default) on project morphia-parent: Error creating blob: cannot retry due to server authentication, in streaming mode -> [Help 1]

From the pom:

<distributionManagement>
    <site>
        <id>github</id>
        <url>scm:git:ssh://git@github.com/jmkgreen/morphia.git</url>
    </site>
</distributionManagement>

<scm>
    <connection>scm:git:git@github.com:jmkgreen/morphia.git</connection>
    <developerConnection>scm:git:git@github.com:jmkgreen/morphia.git</developerConnection>
    <url>https://github.com/jmkgreen/morphia</url>
  <tag>HEAD</tag>

            <plugin>
                <groupId>com.github.github</groupId>
                <artifactId>site-maven-plugin</artifactId>
                <version>0.7</version>
            </plugin>

                <plugin>
                    <groupId>com.github.github</groupId>
                    <artifactId>site-maven-plugin</artifactId>
                    <configuration>
                        <message>Creating site for ${project.version}</message>
                    </configuration>
                    <executions>
                        <execution>
                            <goals>
                                <goal>site</goal>
                            </goals>
                            <phase>site</phase>
                        </execution>
                    </executions>
                </plugin>

Any ideas? Having to remove it to make a release so not a good position to be in.

[astik]

I had a similar problem on a multi-module project. Maybe the fact that there are lots of close push with the same message leads to the problem ... I changed it to :

<message>Creating site for ${project.artifactId} ${project.version}</message>

The following try was a success. But I no information if it was the message change or not that did the trick as it was quite quantic =/

[bashor]

Try to check your authentication parameters (login-password, oauh, ...). I had same problem when used wrong oauth token.

[astik]

Authentication parameters were OK. Two attempts on generating site, without changing anything were leading to 2 different results : 1 was KO, 1 was OK, so it was not a credentials issue =/

[cescoffier]

Check if the url from your pom is correct. The url setting is used to determine on which repository you upload the site.

For example:

<url>https://github.com/ow2-chameleon/${project.artifactId}</url>

[mprins]

sometimes the github api just takes too long causing plugin failure

[jinahya]

Are you using Password Encryption in settings.xml?

[galan]

Had the same problem, searched the web for hours and double checked everything, except one: Two-factor authentication Check your security history on https://github.com/settings/security if you have it enabled you might have a long history of failed logins now. To solve this you have to create a Personal Access Tokens on https://github.com/settings/applications

[RedNapPanda]

I'm getting this issue. And I don't have 2-factor auth. I tried changing the message as well as rechecking my username and pass. still nothing. Any ideas?

[walshta]

I was getting this error using a mutli-module project using version 0.9 and encrypted passwords in my settings.xml. I looked at the other issues and it seems this may be related to issue #55. I changed my version to 0.11 which is suppose to have a fix for that issue.

Here are snippets from my parent pom.xml:

<build>
   ...
   <plugins>
      <plugin>
        <groupId>com.github.github</groupId>
        <artifactId>site-maven-plugin</artifactId>
        <version>0.11</version>
        <configuration>
          <message>Building site for ${project.version}</message>
          <server>github</server>
        </configuration>
        <executions>
          <execution>
            <goals>
              <goal>site</goal>
            </goals>
            <phase>site</phase>
          </execution>
        </executions>
      </plugin>
   </plugins>
</build>

[lwiechec]

I have the same when using our GitHub Enterprise instance. I believe I am setting the correct configuration, and the message I am getting is:

[INFO] Generating "Dependency Convergence" report    --- maven-project-info-reports-plugin:2.8
[INFO] Generating "Dependency Information" report    --- maven-project-info-reports-plugin:2.8
[INFO] Generating "Distribution Management" report    --- maven-project-info-reports-plugin:2.8
[INFO] Generating "About" report    --- maven-project-info-reports-plugin:2.8
[INFO] Generating "Issue Tracking" report    --- maven-project-info-reports-plugin:2.8
[INFO] Generating "Plugin Management" report    --- maven-project-info-reports-plugin:2.8
[INFO] Generating "Project Plugins" report    --- maven-project-info-reports-plugin:2.8
[INFO] Generating "Source Repository" report    --- maven-project-info-reports-plugin:2.8
[INFO] Generating "Project Summary" report    --- maven-project-info-reports-plugin:2.8
[INFO] 
[INFO] --- site-maven-plugin:0.11:site (default) @ bsq-to-dtql ---
[INFO] Creating 27 blobs
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 33.810 s
[INFO] Finished at: 2015-06-21T20:37:34+02:00
[INFO] Final Memory: 30M/741M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.github:site-maven-plugin:0.11:site (default) on project bsq-to-dtql: Error creating blob: cannot retry due to server authentication, in streaming mode -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

[tmjeee]

Same error happening in 0.12 (with just plain username and password in settings.xml, not using encrypted token)

[phavelar]

I'm having same issue here... any solution yet?

[Karm]

@tmjeee @phavelar It works for me, but I had to grant the token additional privileges.

• token in settings.xml
• privileges:
  • repo - Full control of private repositories
  • repo:status - Access commit status
  • repo_deployment - Access deployment status
  • public_repo - Access public repositories
• notifications - Access notifications
• user - Update all user data
  • user:email - Access user email addresses (read-only)
  • user:follow - Follow and unfollow users

(user:follow - probably not necessary, but user:email definitely is)

[edsondt]

I am still getting this error. I wonder if this is because my repo is in a corp server. Where do I specify the GitHub url?

I put in at as <url>https://github.corp.mycompany.com/myname/myrepo</url> in my POM, but I am still getting the "cannot retry due to server authentication" error.

[rexhoffman]

This is likely due to github redirects. You might have an old owner/name for your github project in your url. It'll work, just not for this plugin. For this plugin you need the exact location of where you moved your project to.

[llorllale]

I'm running this in a travis build using an access token.

I struggled with this issue forever until I realized I was using a "-" (dash) character for the environment variable name containing the token. Make sure this is not your issue. Since my repo is public, I only required public_repo access to make it work.

[rehevkor5]

@cescoffier Which <url>? Top-level under <project>, <scm>, or <distributionManagement><site>?

[helloworq]

it is working when i use token as my account not password

[meghadureja]

Worked when I create new access token and then use same token in in settings.xml