I'm deploying an Angular application with this command:
ng deploy --base-href=https://fsalpha.fireflysemantics.com --cname=fsalpha.fireflysemantics.com
It works and this is the repository it's deployed to:
https://github.com/fireflysemantics/fsalpha
I have also setup A records so that the CNAME should work. In other words this url should work:
https://fsalpha.fireflysemantics.com
However after deploying the SSL checkbox does not enable inside Github Pages and the dialog section for Github Pages looks like this. Github pages did not picup the CNAME record and place the value in the custom domain field:
I've tried deleting and recreating the respository, but I'm not having any luck. Thoughts?
Turns out this happens when the first commit to gh-pages is done by a user with non admin privileges.
As long as the first commit is done by a user with admin privileges, future commits from both non admin and admin users will trigger the build.
Related
I am trying to create a dockerfile where nextcloud will be installed through the cli, based on the docker images documented at https://hub.docker.com/_/nextcloud#running-this-image-with-docker-compose.
To test this, I manually run occ maintenance:install in the container, with the relevant parameters for admin user and database. After doing this, I see installed: true in occ status. Also, occ user:list shows me the new admin user.
However, after doing this, when I visit the web UI at http://localhost:8080, I still see the installation screen with "Create an admin account" and an "Install" button.
Also, requests to the ocs API, e.g. http://localhost:8080/ocs/v1.php/cloud/users, don't work.
To move forward and see what happens, I completed the install through the UI, creating a distinct user "admin1".
After doing this, occ user:list shows both the "admin" user from the cli installation, and the "admin1" user from the web UI installation. Also the ocs API works now.
So, what might be missing from the cli installation, that the web UI still thinks I need to install and create an admin user?
The confusion is coming from different installation directories.
The docker image contains one "installation" at /var/www/html and another at /usr/src/nextcloud. The web version uses the former. I suppose the latter is not really meant as an active instance.
For some reason I was using /usr/src/nextcloud/occ for occ. Obviously I had to use /var/www/html/occ instead.
Depending on circumstances, both could use the same database, which would result in users created in web and cli ending up in the same db table.
I have two GitHub accounts set up on my computer. I followed the steps as defined here to create multiple SSH keypairs. I am able to work on multiple repos from different GitHub accounts.
Using my default (work) account I can successfully deploy my Docusaurus website using both approaches: HTTPS & SSH. But when using my personal GitHub account I can not deploy a Docusurus website to GitHub pages. The steps I am following:
git clone git git#github.com-personal:USER/repo-name.git
Next, I locally configure my username & email for git.
Create the template website (i.e. npx #docusaurus/init#latest init my-website classic). Update the docusaurus.config.js file, etc.
When deploying:
DEPLOYMENT_BRANCH=docsites-pages GIT_USER=Username USE_SSH=true yarn deploy
Everything works until the CMD: git commit -m "Deploy website -based on abx..." is executed. The error message:
ERROR: Permission to username/username.github.io.git is denied to OtherUserName
The OtherUserName is my GitHub work account, which is the default in the ~/.ssh config file.
THE PROBLEM - Docusaurus is using the wrong account (i.e. OtherUserName) when attempting to push the generated website to the branch.
Note, that I am using a GitHub pages User site vs a Project site.
I have done simple Drupal 8 installation and while developing was accessing it via it's IP address, now when trying to log in as admin on the actual domain, every time after processing correct credentials it throws "Access Denied".
Google reveals this should be cookie_domain related issue. Tried changing the setting in services.yml to no avail, drush cr not helping. Either the issue is unrelated or the YML settings are not being picked up. Tried VM reboot since to no avail.
Have u checked the clean URL's enable on your site?
Try login your website from the URL: http://www.example.com/?q=user/login
Also I have noticed you have Drush installed. So use the drush for one time login link for user.
eg: drush uli
Hope this helps you.
I have installed moodle many times. But this time when i install moodle all steps are completed uptil update profile. (localhost/moodle/user/editadvanced.php id=2) when i enter admin details and update file nothing is displayed. when i try to access moodle module through localhost chrome displays message "web page has a redirect loop".
localhost/moodle/admin/index.php page is not redirected. i have reinstalled Xampp.
in Apache error log i found following
RSA certificate configured for www.example.com:443 does NOT include an
ID which matches the server name
.
i found solution some where to comment include conf/extra/httpd-ssl.conf but it another error is activated in error log
"Sessioncache is not configured"
. Also i have changed port 443 but it didn't work
Find the moodledata folder.
Inside the moodledata
there are many folders
Delete all from Cache
2.Delete all from Session
Restart your browser.
It worked for me.
Hope that works for you.
Thanks for reply. I have found another solution.
While i was accessing a service provided by Linux server i got message that service has been blocked by security settings. I searched and while searching for that problem i found the solution of both.
https://productforums.google.com/forum/#!topic/chrome/DYk8tSV8qM4
go to control panel, programs, click on java, security.
set security to medium.
Java security was set to high which was blocking moodle application.
Delete the cache and the sesson folder data's in the moodle data folder. It will prevent you from redirecting the loop.
It is worked for me.But deleting the whole moodledata folder is not recommended
Just a guess... but if you are using a certificate, have you tried using https in your config.php?
$CFG->wwwroot = 'https://...'
I've been using Heroku normally in the past few months. In the beginning, I created a ssh key, I added it to my Heroku account and I could deploy my apps without any problem. Until today. I'm working on a new project and I needed to create a new Heroku account under a different e-mail address. After a while I realized I couldn't deploy this app using a new e-mail address because my SSH key was associated to a different e-mail. Then I created a new SSH key and added it to my new Heroku account. It didn't work! :)
Well, I removed the key from my computer and from my new Heroku account. Then I decided to go back to my original Heroku account. Everything works, well, more or less. I can still deploy my old apps, I can see I only have one SSH key there, I can run the commands: heroku info, heroku apps, etc.
So then I tried to deploy my new app, but before I created a new Heroku app using: heroku create. The new app was created successfully. But when I try: git push heroku I get this error:
! Your key with fingerprint
b2:69:3b:90:1e:e1:60:ad:a0:b9:f7:::*:* is not authorized to
access furious-leaf-9996.
If I try: heroku info, I get this error:
! You do not have access to
furious-leaf-9996.
The funny thing is, if I switch to the other app's directory and try to do the same thing (ex.: heroku info, git push heroku), everything works perfectly.
Note 1: When I try heroku logout then heroku login, I'm always able to connect, in both app's directory
Note 2: I'm using RVM and both apps use different gemsets.
I don't know what else to do!! Anyone??
Thanks!
After getting almost crazy I found out what was happening.
When I first tried to login on my second Heroku account, my .git config file was updated with this info:
[remote "heroku"]
url = git#heroku.com:furious-leaf-9996.git
fetch = +refs/heads/*:refs/remotes/heroku/*
And this was the problem. Even logging out and logging in again in different Heroku accounts, every time I tried to push my files there, I couldn't because I didn't have access to this repository. And it got worse because I deleted this repository. :)
Now everything is working properly.
So next time you have access problems on Heroku, take a look at your git config file!
Thanks!