Next.js Discord

Discord Forum

Characters not loading in on certain pages

Unanswered
Tenterfield Terrier posted this in #help-forum
Open in Discord
Original message was deleted.

23 Replies

Original message was deleted
Can you share the component that has issues? Like the code?
Tenterfield Terrier
it works on some pages but not on others, the same exact pages had an issue where other characters didnt show up, switcing them out for their unicode didnt work either
Hmm seems like utf-8 will not be encoded on some pages… what browser are you using? And do the styles and stuff like that load on the „broken“ pages?
Asian black bear
@Tenterfield Terrier hey
Nvm
Original message was deleted
Tenterfield Terrier
yes it is
Asian black bear
Oh
@Tenterfield Terrier can you try the entity ©
Tenterfield Terrier
already did on some other icon that didnt work and I replaced, when using the real unicodes the same thing happend
@Tenterfield Terrier already did on some other icon that didnt work and I replaced, when using the real unicodes the same thing happend
I guess then it’s the best to use an actual icon library like iconify, react-icons or lucide-icons
Tenterfield Terrier
Honestly never thought of that, I had the "•" On my page as well that breaks on the pages too. I do think it's some strange bug tho
@Tenterfield Terrier Honestly never thought of that, I had the "•" On my page as well that breaks on the pages too. I do think it's some strange bug tho
Hmm when I visit the page, then it’s broken for me as well… so can’t be a browser bug… are you using nginx or self host or similar? Or just host on vercel?
@Tenterfield Terrier I self host via nginx
Can you share your nginx config? (Not the whole, only the one entry that serves the url)
Original message was deleted
Can you change your config to include the extra stuff:


server {
listen 80;
server_name $DOMAIN_NAME;

# Redirect all HTTP requests to HTTPS
return 301 https://\$host\$request_uri;
}

server {
listen 443 ssl;
server_name $DOMAIN_NAME;

ssl_certificate /etc/letsencrypt/live/$DOMAIN_NAME/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/$DOMAIN_NAME/privkey.pem;
include /etc/letsencrypt/options-ssl-nginx.conf;
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem;

# Enable rate limiting
limit_req zone=mylimit burst=20 nodelay;

location / {
proxy_pass http://localhost:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;

# Disable buffering for streaming support
proxy_buffering off;
proxy_set_header X-Accel-Buffering no;
}
}



Then restart nginx and check the broken pages again
Tenterfield Terrier
is there anything I should remove ?
@Tenterfield Terrier is there anything I should remove ?
Oh yea, remove all the stuff and add only mine. It should already have everything you need (at least that works fine for me on my server)
Original message was deleted
That looks extremely like AI. Are you sure you know what you doing?
Tenterfield Terrier
eh tbh no, I have also had this set up ages ago and never had any issues, I honestly think this might just be the boilerplate code
Oh ok lol. I guess it has todo with nginx and the serving of the files. As I am not that much experienced with nginx (I like treafik and caddy) I can’t exactly determine the issue, sorry
Tenterfield Terrier
no worries