The unauthenticated git protocol on port 9418 is no longer supported.

The subject pretty much says it all.

TASK [software/rbenv : Add GEM_HOME pathing support]
FAILED - RETRYING: Add GEM_HOME pathing support (2 retries left).
FAILED - RETRYING: Add GEM_HOME pathing support (1 retries left).
fatal: [localhost]: FAILED! => changed=false 
  attempts: 2
  - /usr/bin/git
  - fetch
  - --tags
  - origin
  msg: |-
    Failed to download remote objects and refs:  fatal: remote error:
      The unauthenticated git protocol on port 9418 is no longer supported.
    Please see for more information.

I’m installing on a new Google Cloud Compute instance. I had to open a few additional ports, and added this one mentioned just now… although, I have a feeling it’s saying there’s more than a firewall issue.

localhost : ok=1346 changed=27   unreachable=0    failed=1    skipped=656  rescued=0    ignored=0

Github applied the kill switch on March 15th. It was patched yesterday. Most recent builds look OK.

Run systemctl restart bootstrapper-resume to reapply installation, which should pull from edge before retrying. If not, cd /usr/local/apnscp ; git pull.

my apologies, but I’m not seeing that either of those commands are making any difference.

I’m running the ansible-playbook bootstrap.yml command now, just in case that was part of the process.

Provide output from those two commands in that case so we are on the same page. Additionally, git describe from /usr/local/apnscp.

I’d like to add that this is my first ApisCP install AND that I’m not all too familiar with git-cli.

# git describe

# systemctl restart bootstrapper-resume

# git pull
warning: Pulling without specifying how to reconcile divergent branches is
discouraged. You can squelch this message by running one of the following
commands sometime before your next pull:

  git config pull.rebase false  # merge (the default strategy)
  git config pull.rebase true   # rebase
  git config pull.ff only       # fast-forward only

You can replace "git config" with "git config --global" to set a default
preference for all repositories. You can also pass --rebase, --no-rebase,
or --ff-only on the command line to override the configured default per

warning: no common commits
remote: Enumerating objects: 262, done.
remote: Total 262 (delta 0), reused 0 (delta 0), pack-reused 262
Receiving objects: 100% (262/262), 33.66 KiB | 478.00 KiB/s, done.
Resolving deltas: 100% (57/57), done.
 * branch              HEAD       -> FETCH_HEAD
fatal: refusing to merge unrelated histories

I’m not sure if I figured it out or not, but noticed a few permissions issues in the logs. I noticed a handful of folders/sub-folders as root.root owner/group.

I updated the on folders/files in chown -R apnscp.apnscp /usr/local/apnscp/* and ran upcp -b.

Again… newbie to ApisCP here. But, it does appear to be moving forward with installation. …at least moving forward on something, because it’s taking a while to run through

That’ll also work as well :+1:

took a while to finish up, but it’s looking better:

PLAY RECAP ******************************************************************************************************************
localhost : ok=1501 changed=11   unreachable=0    failed=0    skipped=726  rescued=0    ignored=0