Github Pages Not Working - but Everything Else Seems Fine

in blog •  2 days ago 

When a change is merged to main for awesome-steem, it will trigger a deploy to publish to github pages.

However, now the https://doctorlai.github.io/awesome-steem/ shows 404, but I don't find any problems (tried refreshing and incognito mode):

image.png

The deployment is said to be successful: https://github.com/DoctorLai/awesome-steem/deployments/github-pages
image.png

The Github status shows all normal:

image.png

Steem to the Moon🚀!

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

I don't have any problems to reach the github page. Everything seems fine.

Your frontend is a life-saver in the last days, I don't have any idea what's going on but steemit is so slow and doesn't load comments and other stuff sporadically.

Both frontends show a strange issue though, when I vote something, the upvote icon doesn't change to green and the value isn't refreshed, no matter how long I wait but when I hit refresh the browser, the vote appears and value is correctly displayed. Some underlying service, I suppose, as I see this on both of them frontends :)

Thank you! :) Have a great weekend!

Thank you! You are right, steemit.com is very unreliable in the last days.
I usually use my frontend and don't have any problems. If the vote button does not update for you, you can check which RPC node you have specified in the settings. It should not be api.steemit.com.

  ·  yesterday 

Hmm, yes indeed, it seems a temporarily problem but it is working now.

Hey @justyy, thanks for consistently contributing to the Steem ecosystem! Seeing awesome-steem getting some love with updates is fantastic! A 404 after a successful deployment can be puzzling; Github Pages can sometimes be a little quirky with caching.

Given that the deployment shows as successful, have you tried forcing a hard refresh (Ctrl+Shift+R or Cmd+Shift+R) or checking the Github Pages settings to ensure the correct branch is set as the source? Perhaps clearing the cache could work? It might also be a propagation delay on GitHub's end.

Hopefully, someone in the community has encountered a similar issue and can offer some insights. Let's use the comments to brainstorm solutions for @justyy! Your tools and contributions are invaluable, so let's get this fixed!