2 months ago
I have 1 project with two front end apps and an api folder. It shows on the disk as 300mb roughly in observability stats.
All I am trying to do is add a blank, default WordPress install and it is telling me I am going over by trying to install that. I wouldn't think a WP install would come in at over 4.7gb in size.
Max size of 5000 MB on current plan. Please select a valid size or upgrade
Am I missing something here. I can upgrade but mainly today I am trying to find where to stick some troublesome WP sites, so it is more specific to - is this a good host for WP sites?
Pinned Solution
2 months ago
this is how I got around it. it seems it would reduce the size after the fact. essentially the worker that created the container mentioned just asked for too much hypothetical space.
Still stuck on the 403, maybe I will rephrase in a new more specific thread.
Either way, I upgraded the account to have more build space for the future.
7 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
I am using the agent, this likely has something to do with it. The default deploy threw an apache style 403 forbidden error. So I was trying to troubleshoot and it wanted to remove the volume and recreate it. -- Also it keeps asking me to delete the old volume, while telling me it is done (contradiction)
----
The deployment is still in progress. The real issue is likely that the volume already has stale/incomplete WordPress files from the first failed deployment. We need to clear it and redeploy.
Let me remove the volume and recreate it:
Fetched service config
I see the volume ID: 0....9. Let me remove it and create a fresh one:
Staged volume removal
Remove "primary-volume"Staged
Staged volume: wordpress-data
Create "wordpress-data"Staged
Perfect! I've cleared the old volume and created a fresh one. Deploy these changes and WordPress should initialize properly with a clean slate. You should see the WordPress setup page when you hit the URL.
2 months ago
It is asking me to deploy 4 changes when this error pops up and stops it.
Max size of 5000 MB on current plan. Please select a valid size or upgrade
Attachments
2 months ago
Found out how to cancel deploy.
2 months ago
I have deleted and reinstalled it several times. Still stuck trying to get past the 403 forbidden error.
Forbidden
You don't have permission to access this resource.
Apache/2.4.66 (Debian) Server at primary-production-db5a5.up.railway.app Port 80
2 months ago
i see two separate things going on here, first the size error , when you look at the staged changes in that screenshot, check what size the agent assigned to the new wordpress-data volume, thats almost certainly whats pushing you over the 5000mb limit, not wordpress itself, just set it to something small like 1gb manually instead of letting the agent decide
second the 403 , that error was there before all the volume drama, so deleting and recreating the volume wont fix it, the 403 is its own separate issue and the agent is sending you in circles trying to fix the wrong thing
2 months ago
so cancel the agents staged changes, fix the volume size manually first, then deal with the 403 as a separate problem once youre actually deployed
2 months ago
this is how I got around it. it seems it would reduce the size after the fact. essentially the worker that created the container mentioned just asked for too much hypothetical space.
Still stuck on the 403, maybe I will rephrase in a new more specific thread.
Either way, I upgraded the account to have more build space for the future.
Status changed to Open brody • 2 months ago
Status changed to Solved brody • 2 months ago