Step5.php issue

I am attempting to upgrade my 17.0.2 to 19.0.2 and I keep getting the error message, " This site can’t be reached, the webpage https://*****.net/install/step5.php might be temporarily down or it may have been moved permanently to a new web address." I have confirmed that the file is there via filezilla.
My method of updating was and extract current build
2.copy contents of htdoc to url root directory
3. open browser at url/install/index.php
This seems to work except for this issue and another that it always treats the upgrade as a new install. I have tried opening upgrade.php and upgrade2.php but each gives error that running those files must originate from index.php. Any ideas?

does that file exist in the file system? and what is it’s permissions?

It does exist and both the install folder and the file have full read/write/execute privilege.

You need to copy content htdocs to htdocs not to root. your conf.php will be inside url/htdocs/conf/. Now you do new install because no conf.php in url/conf/

It’s not necessarily wrong that way, especially if you have reconfigured the “root” of your virtual host pointing to the Dolibarr /htdocs directory (that’s how many of us do it). This way, the “sibling” folder (at the same level) /documents becomes naturally inaccessible to web browsers.

Additionally, if you are upgrading from a previous version, you should already have this issue under control. I don’t think this is the problem.

@CharlesAdmin , have you resolved it yet? If so, please share here what the problem was and how you fixed it. Because it will help other users with the same problem in the future.

If you haven’t resolved it, can you paste the contents of the /conf/conf.php file here? Obviously, remove any sensitive data such as passwords, and also change your server username for security :sweat_smile:, if it is part of any file path. You can also mask the database connection details.

Because 80% of problems of this type are related to the absolute addresses defined in that file.

Additionally, another usual step to resolve problems of this type is to check the server log files (apache, PHP…) because more error information usually appears there.