Updated to latest 4.010 version and none of my sites work anymore
-
We can’t connect to the server - that is my current error on all of my Wordpress projects for both front and backend. I did update Laragon after 6-8 months. Was it made backwards incompatible since? Databases and folder structure is still there intact.
-
@Mars-Vertigo : Compatibility is first requirement of Laragon new version. How did you upgrade?
Also, please show me the error messages and images, I will help you sort it out.
-
@leokhoa Well, I downloaded and installed the latest update over the previous version
-
@Mars-Vertigo : You did it right. The upgrade is very simple and safe.
From the image, I don't know why you havewww.
It should be:
http://neroboost.oo/wp-adminPlease check you
hosts
file to make sure.
-
If it don't work, can you change your hostname format to:
{name}.test
(In Menu > Preferences)
-
@leokhoa I am not sure if you meant this hosts file, but I could not find any other. As you can see your http:// solution did not work. In that host file I cannot see any of the links anymore, but perhaps I am just accessing a wrong file. Anyway, even when I manually type in neuroboost.test/wp-admin or anything - I am getting an error. Also I am not really experienced and not a developer.
-
here is the screenshot
-
And after changing the path to test in procfile I am still getting the same error. However, when I try to access the frontend of the WP frontpage I am getting a barebones html without any CSS styling already made to it. What I am doing wrong?
-
@Mars-Vertigo : From the hosts file, I see no DNS entry for your project.
Also, theh
is red means Laragon is not allowed to change your hosts automatically. You may need to run Laragon as Administrator then click reload to force Laragon generate correspond DNSes to yourhosts
file.
-
Ok I did what you said, but the problem persists
-
@Mars-Vertigo : As you changed your hostname format, you should use
xxx.test
not.oo
-
@leokhoa but that's what I get when I click on the link under Laragon host links - on screenshot you can clearly see that host names have been changed to .test, yet when I click or even manually input the link into browser it automatically changes to .oo !! So nothing at all has changed.
Also after http://neuroboost.test:8080/ I am still getting only the barebones http page as if the wordpress and the plugins are not loaded at all.
-
@Mars-Vertigo : Now, it works!
The redirection happens because your database still stores neuroboost.oo hostname.
After running Laragon as administrator, you can change your hostname format back to{name.oo}
and click reload.
The issue will be sorted.
-
@leokhoa ok, so it was all this easy
Just change the test back to oo, it works now. However, I have also noticed another change to the previous version - I can't see ngrok anymore. Is there any other way to share my localhost work in progress online? I also remember that in Laragon it was a painful process, because I had to always switch on relative URL plugin when I wanted to share it.
-
@Mars-Vertigo : The ngrok menu had been moved to Menu > www > Share
Using the relative URL plugin is old way. Just update your wp-config.php:define('WP_SITEURL', 'http://' . $_SERVER['HTTP_HOST']); define('WP_HOME', 'http://' . $_SERVER['HTTP_HOST']);
Note: When doing that you can also change your hostname format to
{name}.test
without worrying about redirection.Ref: https://forum.laragon.org/topic/167/tutorial-how-to-force-wordpress-to-use-relative-urls-ngrok/2
-
@leokhoa well that's weird. I have copy & pasted these lines as you said, but the site gets shared without all the CSS markups simply as barebones page again
-
I have the same problem on Windows 10. I have setup my site as:
ambergristoday.web
However, I get the barebones site. No css working.When I check my Home link it shows like this:
http://ambergristoday.web/localhost/I don't think that localhost should be there, right??
I guess that's why none of the css is loading.I also have another server installed as well, Uwamp. And it does the same thing. Something is wrong with the path.
-
@mousepadsp before the problem was caused by static URLs, you'd have to install relative URL plugin to cater this problem. Leo said above that adding two those two lines of code into config.php would solve the problem, however, it does not work for me. Did you try it yourself?
-
@Mars-Vertigo
Unfortunately I'm testing a drupal 7 installation, so it won't work for me.However, my Uwamp installation was operating well, slow, but was working fine before I installed Laragon. It is only after installing Laragon I noticed the problem with paths on my applications.
I have no clue where to go from here.