-
IssueI've hosted my personal page https://audreyw.top/ on this Github repo, but it does not display properly when opening with Chrome. It only shows text but no theme. However, when I open it with Safari, it displays fine. Initially, I suspected this might be an issue specific to Chrome. However, when I build the site locally and access it at http://127.0.0.1:8000/, everything appears as intended in Chrome. This sounds very bizarre, and any solutions or advice would be appreciated! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Hi Yuxin. Your site definitely does not load properly for me in Safari, but the cause has nothing to do with Pelican itself. I highly suggest that you become familiar with the development tools built into browsers, as they will usually point you in the right direction. This case is no different in that respect, as I see a bunch of errors in Safari > Develop > Show Web Inspector > Console tab that have to do with CORS, re-directs, and loading insecure content. In short, these issues have nothing to do with Pelican itself and everything to do with how modern browsers work (or don't work) with mixed HTTPS/HTTP content loading. |
Beta Was this translation helpful? Give feedback.
-
Problem solved! So as @justinmayer suggested, I checked Chrome's web Inspector and came across the following error:
This error suggest that the Then I checked Safari's web inspector, and I noticed errors related to 'redirection conflict'. This led me to thought the custom domain might be the cause. Previously, I set |
Beta Was this translation helpful? Give feedback.
Problem solved!
So as @justinmayer suggested, I checked Chrome's web Inspector and came across the following error:
This error suggest that the
style.min.css
was loaded throughhttp
while the website was accessed viahttps
. Chrome blocked it sincehttp
is viewed as insecure. Initially, I followed the solutions in this post by changing allhttp://...
links in my pelican config and content files intohttps://...
. But this error somehow persisted even though…