When I try to access the page at https://fabio-laf.github.io/graph-visualization/, it says "404 There isn't a GitHub Pages site here".Am I doing something wrong? The page repo is https://github.com/Fabio-LaF/graph-visualization.
Note: I have already published a page in GitHub pages that works just fine and the settings seem to be the same as this one.
It's working now. You saw 404 because your 404 was cached by your browser. Try open it with incognito mode or clear your browser cache.
If you want to purge GitHub pages cache you can trigger a new build by:
git commit -m 'rebuild pages' --allow-empty
git push origin <branch-name>
Related
I try to install cyberpanal in digitalocean droplet, but it does not install successfully.
After that when i visited my website a '404 not found' default page from LiteSpeed is shown. Also the Apache is not running
Sample Image
If you have an issue with installing the CyberPanel, please consider launching a CyberPanel from the marketplace directly. It should be much easier for you to setup a server.
CyberPanel uses OpenLiteSpeed as a default web server, so you should not expect an Apache run by default.
Before visiting the page, did you create a website on the control panel yet? If not, then a returned 404 status code is expected.
More, https://cyberpanel.net/docs/2-creating-website/
If you have more question for CyberPanel, I'd recommend you ask in their forum https://community.cyberpanel.net/
I created a github page with jeyll as per https://docs.github.com/en/free-pro-team#latest/github/working-with-github-pages/getting-started-with-github-pages
This is my public repo https://github.com/MrBuggySan/mrbuggysan.github.io & this is the github page link https://mrbuggysan.github.io/
I've setup the github-pages dependency on the gemfile and this same repo works for me locally. Is there something I missed here?
First, make sure you have configured the main branch, folder docs, as publishing shource
Second, in that docs folder, you should see what Jekyll has generated: docs the "destination" folder in Jekyll configuration.
(like Jekyll itself does when it builds its documentation)
My Hugo site starts locally, but only returns a 404.html page when hit on GitHub Pages.
I've tried re-instantiating the repo, rebuilding the site with different commands, pushing and deploying with the Hugo deploy script, and rm -rf the public folder and re-adding it.
Repository: https://github.com/jschalz/jschalz.github.io
When following the tutorial, running git submodule add -b master git#github.com:jschalz/jschalz.github.io.git public:
'public' already exists in the index
Currently hosted at https://jschalz.github.io.
I'd expect the site to come up with my pages (and I definitely have non-draft pages on there), but it's only returning 404.html. It's possible it's because I renamed the repo at one point, but I'm not sure. Troubleshooting ideas are very appreciated.
UPDATE: The issue was that I didn't have an index.html, index.xml, or README.md in my repo. Fixed.
2022: A different approach uses now GitHub Actions, since those are the default to build GitHub pages, since Aug. 2022.
Hence the new section "Build Hugo With GitHub Action" and the GitHub actions/hugo-setup.
Original answer 2019:
The issue was that I didn't have an index.html, index.xml, or README.md in my repo. Fixed.
Not exactly fixed.
The point of the tutorial was:
git submodule add -b master git#github.com:<USERNAME>/<USERNAME>.github.io.git public
This creates a git submodule.
Now when you run the hugo command to build your site to public, the created public directory will have a different remote origin (i.e. hosted GitHub repository).
Meaning what you should be pushing if, from your public subfolder, only what Hugo has generated.
You should not push your Hugo project (config.toml, themes, and so on): those should be pushed in a separate GitHub repository for safekeeping and versionning.
I'm working with a website running on laravel. The site works fine on my local through Homestead, no problems.
Recently, I pushed the git repo up to a server that never had this site running on it before. I set everything up right (had some nginx config issues for a while, but got those all sorted out). Nginx has the public folder set as the site root, so it hits the proper index page when you load the page.
What I'm getting is a 500 error. My error logs reveal the following is the reason:
site_root/public/../bootstrap/autoload.php - Failed to open stream: permission denied
in
site_root/public/index.php on line 22
I can confirm that the bootstrap folder and the autoload.php file are both accessible by the web user, and have permissions that should allow access.
I've read a few cases online of people solving this issue with a 'composer install'. I tried updating composer, doing an install, and dumping its cache. I also tried removing the vendor folder (which had been a part of the git repo), and running composer install to regenerate it. None of these have worked. Happy to supply any info that will help. This is Laravel 5.2 running on Ubuntu Server 14.04 with nginx, all on an AWS box.
Solved it. This was actually an issue with site-wide permissions. They were set to 770 instead of 775. I suspect that I can and should restrict them more. For now, I'm just happy to have it loading again.
Moral of the story is to check your permissions site-wide, not necessarily just on the file which gives you the fatal error. You may continue to get the same fatal error, despite permissions being wide-open on the mentioned file. If so, look for permissions issues elsewhere.
I am trying to deploy a webapp to Azure. I am following these directions https://azure.microsoft.com/en-us/documentation/articles/web-sites-python-create-deploy-django-app/
First step, I created a webapp (Django) on the portal.
Then it says to follow the directions to configure Continuous deployment using GIT in Azure App Service. This should apparently lead to my having a local directory of Django files. https://azure.microsoft.com/en-us/documentation/articles/web-sites-publish-source-control/
So I follow those directions, installing Git, creating a local repository, adding a webpage, enabling web app repository, deploying.
The webportal now shows that I have deployed ('active' deployment). However, when I go to the web app url, what's showing is NOT what I deployed, but rather what I guess is the default Django app with its urls (login, logout, contacts).
So then I create an actual Django app in my local directory (instead of the static index.html from the directions). I commit and push it to Azure. It shows as being deployed.
The result is the same as before: the default web app is showing.
So what I'm missing is the connection between my local repository and what's actually showing. Is there some way to pull the Azure default app into my local repository? (Once it's there, I'll be able to change it as I see fit.)
Things are working as expected, but you ended up overwriting the Django app in your first the Git commit. The Continuous Deployment instructions as written are generic to any deployment, even a blank Web App.
So what I'm missing is the connection between my local repository and what's actually showing. Is there some way to pull the Azure default app into my local repository? (Once it's there, I'll be able to change it as I see fit.)
All you need to do is git clone your repo after you've initialized your local Git repo on the Azure Web App. You've already gone through most of these steps, but I'll include them here for others who may be looking for this answer.
After you create the Django Web App from the Azure Marketplace/Gallery, scroll down to set up continuous deployment.
Choose Local Git repo.
Notice that you now have a Git Clone URL in both your Quickstart Essentials info and under All Settings >> Properties. Go ahead and copy this URL.
If you haven't already done so, you may need to set or reset your Deployment Credentials. You'll find this under All Settings. This will be your Git & FTP credentials. Note that this is actually the credentials for your Microsoft Account, not just this one Web App.
You already have Git installed from your first attempt. You should now be able to navigate to the folder you want to clone the repo into and run:
git clone <your_git_clone_url>
After you type in your password, you'll have a cloned repo of the Django Web App on your local system. cd into the directory and start working from there. Once you have changes, git add ., git commit, and git push them back to the repo in Azure to see your changes there.