I have strapi running in EC2 and with elastic IP and it is public, say a.b.c.d
Say
admin panel is : a.b.c.d:1337/admin.
My ALB, I had a target group map to port 1337.
From ALB, I made a rule for https(port 443) based on path for forward, say path rule is ‘/cms/*’ redirecting to my target group on ec2 instance on port 1337.
I don’t believe this forum is the right place to ask anything any more.
It seems dead to me. Discord is the place where everyone is at the moment, albeit it is a super messy place and tough luck if you want to search for some past discussions…
@Kevin_Lee not that I know the answer. But when you put the “url: https:abc.com/cms/admin” into the server.js, did you rebuild the strapi? Basically, this config (and URL for the dashboard in particular) is used when the “yarn build”/ “npm build” is executed.
It gets baked into the webpack bundle and changing it will require re-building the bundle again.
So if you know your dashboard will have to be accessible as “https:abc.com/cms/admin” then set the url to this value and then do yarn build.
I hope this is the reason you are getting 404 at the moment and by following this suggestion you get it sorted…
@aveprik , thanks for the response. I believe i did ‘npm run build’ because we developed some plugins and we realize that webpack isn’t changed so the new things aren’t there. I can give another try. I will try out discord later. are all the devs so overwhelmed at this moment? I did not mind contributing to this open source thing but what is the strategies here. Aim for commercial?