Bad relative path from remote machine on Apache server - wordpress

I installed last version of xampp 1.8.0 in a win 7 pc. I use apache, mysql and wordpress 3.4.2
I buit a new web site on htdocs and all work good locally (as a localhost , 192.168.1.10).
But when I try to access from another pc on the lan to 192.168.1.10 my web site it only shows a homepage without images and all path have link to localhost instead to 192.168.1.10.
Can anyone help me to resolve this issue ? what luck to my configuration ?

In your wordpress admin dashboard, make sure under "General Settings", the Site Address (URL) and WordPress Address (URL) both say "192.168.1.10" instead of "localhost".

Related

AWS EC2 instance showing IIS Page on Public IP even though localhost shows WAMP

I created a Windows 2016 Base EC2 Instance and installed IIS on it. But soon realized that I have to run WAMP to host PHP sites so I installed WAMP and stopped IIS service and everything was working fine.
Then I made a few changes to the site (It's a Wordpress site) and published it and since then the public IP is showing IIS page.
I have tried renamed iisstart.html to iisstart (to trick system into
thinking the file doesn't exist) from IIS folder but the public IP
is still showing IIS page.
I have tried restarting the instance machine. Localhost is showing my wordpress site but public/elastic IP shows IIS.
I have tried restarting WAMP, no luck.
I don't know how is it possible that IIS page is shown even when the file is renamed.
I have tried creating an Elastic IP as well but didn't worked.
Ok! So the issue is fixed! Now posting solution for anyone who will reach here (maybe my future self)
There was no issue with AWS EC2 or WAMP. The issue was in importing Wordpress.
When I imported Wordpress the Site Address and Wordpress Address changed to localhost. Due to which the IP was redirecting to localhost of destination machine.
Solution:
After you import your Wordpress, goto wp-admin -> Settings (in Side Bar)
And change the Site Address and Wordpress Address to the public/elastic IP of your instance.
Then clear Cache/Cookie on your destination machine and revisit the IP. It should work. (It did in my case)

Being redirected to 127.0.0.1 from Wordpress/Apache installation with AMPPS

I have installed AMPPS (Apache + MysQL) with Wordpress on a Windows 10 computer to quickly setup a website. The website is working fine locally.
Now, the problem that I have occurs when I try to access the website from another computer.
When I enter the server IP ( http://219.223.239.3/ ) on another computer, a main webpage show with the main directories:
This indicates that the other computer can connect to the server.
However, when I try to access the WordPress subdirectory on the server ( http://219.223.239.3/wp/ ), it redirects to http://127.0.0.1/wp/ and the webpage does not show. Hence, it seems that there is some configuration problem with WordPress or Apache.
To try to solve the problem, in Wordpress, I went to Settings>General, and I have set the "Wordpress Address" and "Site Addresss" to http://219.223.239.3/. Moreover, I have edited the Apache configuration file to change "ServerName" to 219.223.239.3:80. But it still does not work.
Otherwise, all the settings should be the default settings of AMPPS.
I am not very familiar with Apache.
Does anyone knows how to solve this issue?
Check the wp-config.php file in the root of your wp folder. I had the exact same problem and it turned out the credentials for establishing a connection to the MySQL database I had running locally were incorrect.
In the Ampps management console (typically located at localhost/ampps/ in your brower), open up PHPMyAdmin and check the user credentials for the database connection.

Wordpress website login issue after laptop shutdown

wordpress browser screen shot
I am a beginner with wordpress.
I just created a website locally on my laptop. The default page of 'Hello World' also came up.
But then i 'Shut down' my machine. When i started my laptop again, i am unable to view the 'localhost' website created.
The url i am trying is -
http://localhost/wordpress/
I have installed xampp inside -C:\xampp\htdocs\wordpress
My xampp control panel is running and Apache and MySQL module services are running.
Am i missing some setting? Can anyone please help?
Regards,
Ravi
Your screenshot shows Apache is listening on ports 4443 and 8080, but the url in your address bar is http://localhost/wordpress. Since that URL does not specify a port the default 80 will be assumed. Try http://localhost:8080/wordpress instead.

No theme files found in LAN in Wordpress

i am having a problem with my Wordpress instalation when i try to see my localhost in other computer inside the same network with the ip 192.168.1.201.
For example the code resolves in both browsers as:
And the PC in the network that don´t have those files in localhost, it doesn´t load the resources.
How can i fix this to both in internal LAN? Any kind of redirect ?
Thanks
I don't fully understand your question. If you want to browse your localhost site from other computers on same IP, you should use
http://yourcomputername/wordpress_site/
"yourcomputername" is where you installed the wamp / xampp
Also You should have to change WordPress Address (URL) and Site Address (URL) to
http://yourcomputername/wordpress_site/
In wordpress Settings > General
http://localhost
will only work on the computer where you installed wamp

Drupal Multisite, MAMP and SVN Best Practices?

I successfully set-up Drupal Multisites with:
site1.domain.com
site2.domain.com
site3.domain.com
using Virtualhosts and editing the etc/hosts with MAMP on my localhost. I then deployed it using SVN (it deploys automatically) on the live site.
The Problem: when I type "Site1.domain.com" because it goes to my localhost instead of my live site. Is there anyway to avoid this? (apart from renaming the subdomain, because it speeds up deployment)
Just check your virtual host settings in httpd.conf file, are you using IP address to redirect them?
And if its directing to your localhost, just check your host file, if might be redirecting because of that

Resources