Actually, now that I’m on a different machine and it works… I think it may be something environmental. Sorry!
Hi, @akulbe. It does work when I test as well.
TTL values (time to live values) in the previous, not the new, DNS records are often the root cause for delays in changes to DNS. There is more about this behavior (which true for all DNS - not just sites or DNS at Netlify) here:
If there are other questions about this, please let us know.
I am also having a similar problem of not being able to publish my website on github.
I deployed the code and in my page, it says the site is published. I also downloaded my deploy log and the root file contains index.html. But I still cannot access the domain of my website ~github.io/. Could anyone please help me in solving this issue?
Thanks in advance.
@jooy Welcome to the Netlify community.
Please help us help you by writing a good post!
All issues: Provide your Netlify site name (e.g. gifted-antelope-58b104.netlify.app).
DNS or SSL issues: Tell us your custom domain(s) (e.g. mycustomdomain.com), and how long it has been since you made changes to your DNS (DNS changes can take up to 48 hours). We can’t help if we don’t know your domain.
Build issues: Tell us about your workflow, including what SSG you are using.
If you are deploying via git, give us the URL of the repository.
Let us know what you have already tried and what the results were.
The better the post = the faster we can help!
My Netlify site name is gallant-haibt-7c9b31.netlify.app
And my git repository URl is (https://github.com/juliajoo/juliajoo.github.io).
@jooy Your site seems to be loading for me. Are you certain this isn’t a local issue, perhaps with your browser cache, VPN, etc?
I don’t think so, because if I also run juliajoo.github.io on safari browser, it still shows me this 404 error message.
@jooy Sorry, but I don’t have the patience to troubleshoot an issue with Github Pages. There are many reasons why I use Netlify instead of Github Pages. If your site is loading on Netlify, I recommend turning off Github Pages for this site, which solves this problem.
Thank you for the advice. I unpublished the github pages for the repository, redeployed it via Netlify but somehow I still see the same URL ~github.io on my main site overview page. And still it shows 404 error. Do you have any idea how I can fix this problem?
hey @jooy, i’m not sure i’m following. can you please try and explain in a different way what you are trying to do?
you won’t be able to serve a netlify page by pointing your browser to a github pages address (or vice versa.)
@jooy You’ve made another change, too, because now your site isn’t loading.
What are the steps someone else can take to try to reproduce this?
ye I went through other sources and realized that it won’t work as far as the webpage is in the gh-page repository as mentioned here: https://www.aleksandrhovhannisyan.com/blog/github-pages-vs-netlify/
I quite didn’t know how to move it to other repository, so I just deleted the current one and reforked it. And didn’t made it into gh-page but instead linked the repo right away with netlify. Now it works! thanks!
sorry for the confusion! I didn’t realize the old link was still here in the community. Even after I unpublished the repo, it kept linking me to ~github.io, so I just deleted the repo, reforked it, made new repository and linked it right away to netlify without creating a gh-page. And now it works, thanks for your advice pointing out the gh-page & netlify crashing!
But if I git pull and push changed code to the github repo (which is not gh-page but directly linked to netlify), would the changes well updated on to the published webpage?
I am trying to deploy my site to laughing-haibt-2bc0ac.netlify.app
Deploy is “Published” (like on the screen from OP)
The site is built using a single HTML-file from my Github (50MB of size, isn’t it a problem?)
However, I still see “Page not found”
@lifegivesyoulemons Welcome to the Netlify community.
Your page is loading, but there’s something wrong with your code because it’s not showing anything. It’s also taking forever, which may or may not be related.
WARNING: This file appears to be toxic. I’ve tried opening it in three different text editors and it crashed each of them. My text editors virtually never crash. Be very careful examining the source code of this site.
i didn’t try opening it like gregraven did, but i also see a blank page (not page not found).
@lifegivesyoulemons, does this run locally? a 50MB file is a bad idea on our servers anyway - they are really optimized to serve the small assets generally used by static sites.
And it renders properly on localhost. Moreover, I deployed it on GitHub pages, and it displays the map: sobornist.github.io
If netlify does not manipulate an html before rendering, then it should’ve been ok
We don’t manipulate anything if you don’t tell us to. Do you have your site configured to optimize assets? If not, we are serving what you deployed.
As Perry said, our CDN is not really designed for 50MByte files (we cannot cache files that large on our CDN, so we have to serve from our backing store which is MUCH slower) - so even if it works, performance will be terrible. If you need content that large, you should probably use a different hosting service for better results.
If you are using quasar to build and deploy in netlify, you will get ‘page not found’ first.
The reason is, quasar builds the application with in the folder ‘dist/spa’ (if your application is a single page application -spa). But Netlify looks for the index.html file in the ‘dist’ folder only. obviously our index.html is not there within ‘dist’. It is there in ‘dist/spa’.
To overcome this problem, provide ‘dist/spa’ in the deploy settings ‘publish directory’. This should solve the problem.
check where the index.html is built.
which tool are you using to build?
in any case, check where the index.html is available. you can do this by looking at the deployment log or simply download the deployed site as zip file and browse through.
In my case, I built the app through quasar (vue app), and it was throwing the same error.
my index.html was in ‘dist/spa’. I had to give this in the deployment setting - publish directoroy.