ssirag

Update: I got it working via LDAPS, and the user/pass is now successfully secured. Still not clear about the TLS issue.

Additional issue: background color customization is limited due to the “lost password” link being a grey color. Can the color of that link be customized as well for better visibility?

Yes, I tried to pull first but it wouldn’t overwrite the local files until i did the hard reset.

OK, we got it working. Found 2 specific issues:

1. I had an “@” in my bitbucket password, which is why the https config was failing.

2. As we were dealing with an existing repo, we had to run this on the local server repo in order to get it working first time:

git fetch –all
git reset –hard origin/master

Everything is owned by www-data…

the ‘which git’ function returns:

/usr/bin/git

The local repo was created via command line.

Same error when using the https URL of the repo.

OK…I’ve resolved the local permissions issue…now however it seems to be having a remote authentication issue. I get “Error pushing to the remote repository. The remote repository could be ahead, or there may be an authentication issue.”

From the root command prompt, however, I can run a full commit and push cycle with no issues.

I’ve added the private key that authenticates this server with bitbucket in the /var/www/vhosts/.ssh directory. Is that the right location?

I’m creating a proof-of-concept site to test the viability of building the S3 CDN into all our WordPress sites. I set it up with the AWS credentials in the wp-config.php, and I had the same problem identified above. I removed the wp-config credentials and added them via the web form in the AWS plugin, and it worked.

I used this page for config guidance (especially the IAM permissions policy)

https://blog.celingest.com/en/2013/07/19/tutorial-creating-cdn-wordpress-cloudfront-s3/