# really stumped with home page in production not rendering changes.
Unanswered
Phalène posted this in #help-forum
PhalèneOP
Got a weird issue I can't figure out. Been using Next.js since version 12. Now working on latest v14.
Up to now, I've only pushed to production on amplify, cdk, SST and I want to self-host on VPS to simplify things (other frameworks are moving too fast or too slow, with many things breaking or not yet supported).
Got everything set up from local push-->github actions-->build/push docker image-->caddy/docker-compose on ec2 instance.
Website renders per expectations. BUT...
The home page will not render with the latest modifications. I've tried:
1/ Force headers on it, the builds indicate it is a dynamic page
2/ Added a fetch with some toy data
3/ Added a redirect to another page as soon as the site is hit
4/ Added other folders/pages with client components and server components which render fine.
5/ Added "no-cache" to fetch
6/ Added a short "revalidate" time
7/ Deleted all images from VPS to ensure docker-compose grabbing the latest although I have tagged as "latest"
8/ Set nextConfig with output: "standalone",
The original next.js home page graphics remains. If I build the docker images locally and run, they reflect all the changes to the home page I expect. I am completely at a loss about this.
next:14.2.7, react:18.3.1, react-dom:18.3.1, tailwindcss:3.4.1, node 21.x
Appreciate any tips, tricks, etc.
Up to now, I've only pushed to production on amplify, cdk, SST and I want to self-host on VPS to simplify things (other frameworks are moving too fast or too slow, with many things breaking or not yet supported).
Got everything set up from local push-->github actions-->build/push docker image-->caddy/docker-compose on ec2 instance.
Website renders per expectations. BUT...
The home page will not render with the latest modifications. I've tried:
1/ Force headers on it, the builds indicate it is a dynamic page
2/ Added a fetch with some toy data
3/ Added a redirect to another page as soon as the site is hit
4/ Added other folders/pages with client components and server components which render fine.
5/ Added "no-cache" to fetch
6/ Added a short "revalidate" time
7/ Deleted all images from VPS to ensure docker-compose grabbing the latest although I have tagged as "latest"
8/ Set nextConfig with output: "standalone",
The original next.js home page graphics remains. If I build the docker images locally and run, they reflect all the changes to the home page I expect. I am completely at a loss about this.
next:14.2.7, react:18.3.1, react-dom:18.3.1, tailwindcss:3.4.1, node 21.x
Appreciate any tips, tricks, etc.
10 Replies
PhalèneOP
I haven't. Will give it a try in next 24 hours
@Phalène Got a weird issue I can't figure out. Been using Next.js since version 12. Now working on latest v14.
Up to now, I've only pushed to production on amplify, cdk, SST and I want to self-host on VPS to simplify things (other frameworks are moving too fast or too slow, with many things breaking or not yet supported).
Got everything set up from local push-->github actions-->build/push docker image-->caddy/docker-compose on ec2 instance.
Website renders per expectations. BUT...
*The home page will not render with the latest modifications*. I've tried:
1/ Force headers on it, the builds indicate it is a dynamic page
2/ Added a fetch with some toy data
3/ Added a redirect to another page as soon as the site is hit
4/ Added other folders/pages with client components and server components which render fine.
5/ Added "no-cache" to fetch
6/ Added a short "revalidate" time
7/ Deleted all images from VPS to ensure docker-compose grabbing the latest although I have tagged as "latest"
8/ Set nextConfig with output: "standalone",
The original next.js home page graphics remains. If I build the docker images locally and run, they reflect all the changes to the home page I expect. I am completely at a loss about this.
next:14.2.7, react:18.3.1, react-dom:18.3.1, tailwindcss:3.4.1, node 21.x
Appreciate any tips, tricks, etc.
not sure if related, a few months back i encountered a "weird" docker behavior where i accidentally set a base image as the image name of said service, and use the
something like:
the odd thing is that as soon as i have built the image safe and sound, as i tried rebuilding the image again, the image
build directive to point to a dir with Dockerfilesomething like:
services:
frontend:
image: node:20-alpine
build: ./path/to/projectthe odd thing is that as soon as i have built the image safe and sound, as i tried rebuilding the image again, the image
node:20-alpine got overwritten by the result of the build; which in my case, returned a lot of errors. do you happen to have the same issue?you should try deleting the image and try rebuilding it again to see if that changed the resulting image
also sharing the dockerfile and compose would be very useful
@Anay-208 | Ping on replies Have you tried deleting `.next` folder
PhalèneOP
Hmm, .next folder is in .gitignore and rebuilt when I push the code to github actions
@iyxan23 not sure if related, a few months back i encountered a "weird" docker behavior where i accidentally set a base image as the image name of said service, and use the `build` directive to point to a dir with `Dockerfile`
something like:
yml
services:
frontend:
image: node:20-alpine
build: ./path/to/project
the odd thing is that as soon as i have built the image safe and sound, as i tried rebuilding the image again, the image `node:20-alpine` got overwritten by the result of the build; which in my case, returned a lot of errors. do you happen to have the same issue?
PhalèneOP
i build the image on github actions then push the image to the ec2 server so the image has a custom name
PhalèneOP
going to try swapping out alpine and using ubuntu slim, to see if it's something missing from the former
PhalèneOP
that didn't work. I've even removed the home page completely, get a #404 when i build and run locally, still get a home page on remote. It's bizarre.