hi,
after updating to version 3.3.3 the page gives me a 500 error.
the site is on shared hosting and i use php 8.4.1
some help please
1 Like
@altix Sorry to hear you’re having trouble.
Can you provide the specific error you encountered? It will be in your Apache server logs.
It might be related to your PHP version. We only test against PHP 8.3 currently.
I can’t find the logs because I’m on shared hosting and I don’t have access to the Apache logs, the site shows no signs of life, now I’m trying to directly install a new instance with the latest update. Going back to the backup version I have no problem
I also tried with php 8.3 but same error…
1 Like
Without access to error logs it will be impossible to debug. What hosting service do you use? Most provide access somewhere. Try searching your hosting provider’s help resources.
@altix Just checking: you are backing up your code and database before attempting updates, and rolling them back after errors, correct?
yes
1 Like
i use ovh
Just to check the easy stuff, did you navigate to the update.php page and did that succeed?
1 Like
Of course I can, it makes me update the database with 2 updates, after the updates are applied the site goes into error 500… blank homepage
Ps the 3.3.2 version work fine
1 Like
Do you have any other modules, custom code, or customizations? Or is this a relatively “stock” farmOS installation?
I have only two community modules : google maps and custom map layer, then the rest is unchanged
1 Like
blank homepage
Is it possible to access /admin/reports/dblog? That may also show some error logs, and sometimes that still works even when the homepage or other pages are broken. But if you’re hitting a deeper error then it may not even make it into those logs. That’s why you need to be able to check your Apache logs - it’s the best way to find out what’s happening.
I have already tried to access those logs, the update.php page also suggests it, but the page is blank
I’m trying to do a clean install
1 Like
I did a clean install of farmos 3.3.3 but I get an error as soon as it finishes installing the modules:
No route found for "GET…
1 Like
Hmm someone else experienced something similar recently, but I’m not sure if they ever figured out the cause…
I wonder if you uncheck all modules during the farmOS installation… maybe we can trace it to a specific module.
But really, it’s all just a bunch of guessing if you don’t have access to Apache logs. Any progress on that?
this error is a mapbox module maybe…
I managed to do a clean installation but now I have to import all the data… csv doesn’t work on this version…
I was considering passing on the data I had in the previous installation but the csv importer doesn’t work for land and logs
@altix Have you given up trying to figure out what caused the 500 error after updating? That should be the focus of this thread. If you are instead trying to start from scratch and are experiencing trouble importing data, that’s a separate issue.
Or, maybe they have the same cause… which is why I would recommend figuring out how to find your Apache error logs, rolling back to your previous database snapshot on 3.3.2, and working to solve the original update issue. That’s the easiest way to solve this.
1 Like
I’m working on the cause of the error, in fact I sent a request to the host, but they haven’t responded yet. In the meantime I created a new instance but I’m also having problems with the new installation… maybe there is a connection
1 Like