Skip to content
Grav 2.0 is officially stable. Read the announcement →
Support

2.0 migration on nginx problem

Started by Rick Beebe 1 week ago · 3 replies · 147 views
1 week ago

First, I want to say that the migration plug-in is genius. I feel so much more comfortable than using an in-place upgrade. So thank you.

Second, a comment on the documentation. You have a note:

The whole flow is admin-driven and starts with switching your GPM Releases channel to testing, where the migrate plugin and the 2.0 release artifacts currently live during the RC period.

Once you've flipped that switch:

The problem is that you don't say how to flip that switch and I'm probably blind but I didn't find it. BUT the "install migration plug-in" was on the dashboard so I just kept going.

Third, everything went swimmingly until step 5. I'm running on nginx. A minor quibble--the "Manual config snippets" doesn't appear to be a link and it took me a bit to find it. Once I did, I added the nginx block as shown, aside from tweaking the fastcgi_pass to match what I'm using. But when I connect to /grav-2/ the server loops between "/grav-2/" and "/grav-2" a dozen or so times until the browser gives me the "this website can't be displayed" error.

Any idea where I've gone wrong? Thanks.

7 days ago

I am also running nginx and had tried several times to use the migration plugin. All looks great with green light until the last step where it says to test the site. When I click on the link, the homepage appears and I can see that is is pulling from grave-2 folder. However, when I start to browser other tabs, it reverted to the old folder which gives me 404 page not found error. Yes, you are correct about the part where we need to add a block if running nginx, but it doesn't mentioned what block.

Long story short, I just manually upgrade to Grav2.0. I download a fresh Grav2.0 with admin. Test to make sure the Quark2 theme is running fine and able to log in to admin. Then, I added my theme folder, install all the necessary plugins and adjusted some settings. Yes, it is a bit of work, but I am on 2.0 now.

last edited 07/19/26 by Duc
7 days ago

I'll throw some more info in there. I temporarily got around the redirect problem by removing the block and just changing my root directory to /var/www/html/grav-2. And a new issue appeared. Or rather, most of my pages disappeared. My top-level navigation menu is defined as:

TXT
01.home
  blog.md
02.join
  page.md
03.youth-events
  page.md
04.newsletter
  default.md
05.resources
  page.md

I get a 404 on the main page and the only menu item showing up is Newsletter. There are three sub-pages under Newsletter but only one of them is there. The files are all in the tree with proper permissions. I thought maybe the page type but changing the others to default.md makes no difference.

6 days ago

Ok me and the migration plug-in were both being stupid. My other pages were missing because they weren't copied. I manually copied them and they seem to work now. I'm still at a loss as to the proper juju to get the redirect to /grav-2/ working without making it the root though

Suggested topics

Topic Participants Replies Views Activity
Support · by Anna, 2 days ago
3 57 4 hours ago
Support · by TomW, 2 days ago
2 57 4 hours ago
Support · by Anna, 5 days ago
7 176 1 day ago
Support · by Anna, 5 days ago
9 145 1 day ago
Support · by stuart young, 5 days ago
2 94 4 days ago