Followed trouble shooting advice, and still receiving 404 error when trying to deploy to GitHub Pages #23538
-
I have been trying to publish my portfolio website to GitHub pages under the following link: https://lukeqanderson.github.io/portfolio/ However, every time I try to deploy it shows that it failed. I have changed my main repository to master where all my files are located, ensured that master is selected under the pages setting and deleted the README file to test if that resolves the issue. Here is the link to my repository:
GitHub - lukeqanderson/portfolio: A portfolio website created with HTML, CSS...A portfolio website created with HTML, CSS and JavaScript to showcase responsive functionality without implementing any additional styling frameworks. - GitHub - lukeqanderson/portfolio: A portfol... Any help would be greatly appreciated! Thanks, |
Beta Was this translation helpful? Give feedback.
Replies: 12 comments
-
I just checked your page and it is still 404 create a new repo like by this way, before you put any build files you know that your GitHub Pages is working, then you can push all of your build files after |
Beta Was this translation helpful? Give feedback.
-
Was able to resolve this issue. For those running into similar issues, I had received the following error: Error: Error: No uploaded artifact was found! With some further investigation, I realized that I had made a submodule accidentally (I’m still learning git), which contained a copy of my repository. Once I deleted the submodule (name “portfolio” in my case), I was able to deploy with no issues. |
Beta Was this translation helpful? Give feedback.
-
A noob with Github Pages here, I too am getting the same errors. What does “I had made a submodule accidentally” mean. I don’t think I’ve done anything like that |
Beta Was this translation helpful? Give feedback.
-
Hi methodphoto, More or less I created a copy of my entire repository within my repository so it was showing up as a submodule. I would push from this submodule to my GitHub. When it came time to try and deploy the site, GitHub wouldn’t deploy it because it wasn’t sure what to do with the submodule. Since I didn’t need it, I deleted it and resolved the problem. It looks as though your site is now up and deployed. Is it another site that is affected or were you able to resolve the issue? |
Beta Was this translation helpful? Give feedback.
-
Hi Luke Yes in the end I took the approach of starting again with a minimal site, that worked, and just added new parts bit by bit. Thanks for responding :grinning_face_with_smiling_eyes: |
Beta Was this translation helpful? Give feedback.
-
I was experiencing similar issues. I resolved it by creating GitHub staff should look into this newly introduced problem. |
Beta Was this translation helpful? Give feedback.
-
Hi all, While I have some experience on deploying at GitHub pages, this time it also gives me the same error message:
update · gulinan/montpellier_ml_talk2022@488169fContribute to gulinan/montpellier_ml_talk2022 development by creating an account on GitHub. for this repo: GitHub - gulinan/montpellier_ml_talk2022. I will also appreciate any help/suggestion for getting rid of this error (i checked submodule thing, deleted all the files, created new repo, but nothing solved the problem). Thank you very much. Gul |
Beta Was this translation helpful? Give feedback.
-
Hi gulinan, Sorry for the delayed response. I took a look through your repository and came across the following error under jobs → build: “Liquid Exception: Liquid syntax error (line 113): Variable ‘{{i}’ was not properly terminated with regexp: /}}/ in index.Rmd” I’m personally not familiar with liquid, but I was able to find a similar issue to the one you are experiencing that looks to be closed:
Liquid Exception: Liquid syntax error (line 123): Variable '{{0,1}' was not properly terminated with regexp: /\}\}/ in xxx.md
<!-- Hi! Thanks for considering to file a bug with Jekyll. Please take the tim…e to answer the basic questions. You can convert `[ ]` into `[x]` to check boxes (or submit and check.) If there is no need for certain fields like output and redirection, please delete those headers before submitting. We know not all tickets require those steps. Otherwise, please try to be as detailed as possible. If you are unsure this is a bug in Jekyll, or this is a bug caused Please make sure to mention an affinity team whose responsibilities Thanks!
<!--
My Reproduction StepsAfter
But nothing in line 123 as http://pastebin.com/vZszwbvt When I change line 134 from It fixed ! <!-- If you have trouble finding your logs, please email support@github.com and <!-- If your steps are complicated, you can also submit a GitHub The Output I Wanted<!-- /cc include any Jekyll affinity teams here (see https://teams.jekyllrb.com/ for more info) The solution seems to be: " Wrap that whole line with for your variable “i” on line 113 in index.rmd. I’m still a GitHub noob, so I apologize if this is something you have already tested. Hope it helps! Luke. |
Beta Was this translation helpful? Give feedback.
-
Hi lukeqanderson, I would like to apologize for replying your email very lately. This was an extra ordinary week, where i was dealing with paper grading along with the problems which current situation of pandemic brought. I just tried your solution, but, I could not let it worked. I am also not a guru on this. I will leave it as it is. I would like to thank you very much for your kind reply one more time, and would like to apologize for being late million times. I would appreciate your understanding. Best wishes. |
Beta Was this translation helpful? Give feedback.
-
Hi Luke, |
Beta Was this translation helpful? Give feedback.
-
I’m afraid you’re looking at the wrong error. The deploy jobs failed simply because the build job failed. The build job seems to have issues with an invalid date format: Updates · HowieWork/howiework@a66435d · GitHub Your problem seems unrelated to the original post, in the future please create a new thread for that. |
Beta Was this translation helpful? Give feedback.
-
Thank you so much. Yes, I found the problems. |
Beta Was this translation helpful? Give feedback.
Was able to resolve this issue. For those running into similar issues, I had received the following error:
Error: Error: No uploaded artifact was found!
Error: Error: No uploaded artifact was found!
With some further investigation, I realized that I had made a submodule accidentally (I’m still learning git), which contained a copy of my repository. Once I deleted the submodule (name “portfolio” in my case), I was able to deploy with no issues.