I have installed a xampp server in a computer A.
now i want to access this xampp server from other computer B.i typed the ip address of the computer A ,where xampp server is installed , in the browser of computer B. i landed to the **http://XX.XX.XX.XX/xampp** page. now i want to access the htdocs directory but i am not able to access it.i used this path.
http://XX.XX.XX.XX/htdocs
and
http://XX.XX.XX.XX/xampp/htdocs
I am getting error
Object not found
Somebody please explain what i am doing wrong?
First of all you have to see the permitions of the xampp (they are blocked by default and you can see it at php.ini if i recall well) and the firewall of the computer B. After that, you should see the port of the xampp in the computer B and you should see the localhost of that computer.
If you are doing that in differents places, you should see if your operator allow you to see a ip remotely. In some countries are blocked too.
Related
Website with ssl on wordpress. Moved it on localhost, changed wp-config, changed https://olddomain.ru to http://newdomain.ru.
But still have error ERR_SSL_PROTOCOL_ERROR in browser and Invalid method in request \x16\x03\x01 in apache2 logs.Trying to start it via MAMP. How to disable SSL?
This question relates to current and previous MAMP and MAMP PRO versions. MAMP PRO assists in replicating basic web host production environment on a users local Windows based system.
First, it's best to isolate the problem by disconnecting your system from internet.
Turning off GroupStart for Apache and MySQL by un-checking "Include MySQL in GroupStart" is another isolation problem solving technique:
https://documentation.mamp.info/en/MAMP-PRO-Windows/Servers-and-Services/Apache/
https://documentation.mamp.info/en/MAMP-PRO-Windows/Servers-and-Services/MySQL/
Emptying logs by erasing the log files prior to trying out the steps below is another way to isolate problems:
C:\MAMP\logs
Most local systems have AntiVirus program and the antivirus program usually has software firewall bundled. Be sure to add Web Server and HTTPS ports under ports and services of your choice of AntiVirus software.
1. Custom Domain:
First issue is related to assigning custom domains. A custom domain is assigned by modifying Windows Hosts file to point localhost host with IP 127.0.0.1 to a fictitious domain name.
Here is how the default hosts file looks like:
https://support.microsoft.com/en-us/help/972034/how-to-reset-the-hosts-file-back-to-the-default
Here is the required modification:
hosts file
127.0.0.1 newdomain.ru
::0 localhost
::0 is the bus/port designation of a systems network adapter. Usually the first available network adapter software on a device has ::0 address.
After modifying hosts file be sure to flush dns by using Windows command prompt:
ipconfig /flushdns
2. Location of Virtual Hosts data
MAMP documentation recommends you store virtual Hosts data outside of default C:\MAMP\htdocs directory.
https://documentation.mamp.info/en/MAMP-PRO-Windows/First-Steps/View-Localhost/
3. Serverside language application
MAMP recommends to serve serverside language applications such as WordPress on port 80 in your local development environment.
https://documentation.mamp.info/en/MAMP-PRO-Windows/Troubleshooting/WordPress/WordPress1/
I want to show my client the WordPress website on localhost being developed by me (it's still in the beginning stage, not ready to go live yet). This is what I have done so far:
- I have done port forwarding and have tested it (whenever I access my Xampp localhost from the remote network by entering my computer's ip, it opens up the localhost dashboard).
Now this where I'm stuck:
- Whenever, I specify a directory of website (in htdocs) on my remote network's url (like this: mycomputer's ip/folder's name it changes the url to localhost/folder's name and the page doesn't open).
How do I resolve this issue?
Add this line to your wp-config.php might help:
define('WP_HOME','http://your-computer-IP');
define('WP_SITEURL','http://your-computer-IP');
and comment or delete that line when your work from home.
But there's something can be improved. Try to some DDNS services and install their application to your local machine. After installed, you can access your computer from mymachine.ddns.net even you're home or not. So with below setting, you no need to edit anything when you change your work location.
define('WP_HOME','http://mymachine.ddns.net');
define('WP_SITEURL','http://mymachine.ddns.net');
I have XAMPP running fine on one machine and I have 2 WordPress installs running fine on that machine. I would like to be able to access and work on those WordPress installs on other machines on my network.
Right now, I have it set so that if I try to access those directories from another computer on the network, all I get is either the XAMPP splash screen, or a 404 error if I try to access specific folders.
I've researched this and researched this and I have found numerous posts about how to do this.... but only in bits and pieces.
Does anyone know of a step by step, start to finish, guide of how to do this? In layman's terms?
Remote (from another network) would be great too. But I'll cross that bridge once I figure this out.
Any help would be appreciated.
Thanks!
I would suggest rather than shared folders you use an FTP client / server - I use Filezilla server and client for my local sandbox testing server. This will give you additional info like file and folder groups and permissions.
Got to ask the question what OS? have you opened port 80 on the server machine?
Things like this can also occur on Linux if the folders and files do not have the correct groups for access and or permissions.
chown -R apache:apache /var/www/html
the above if on linux will assign all the folders and files to be accessed by the apache process. not having the correct groups assigned can give you 404 when you know the files are actually there.
also check the file and folder permissions,
different files and directories have permissions that specify who and what can read, write, modify and access them - this wordpress page gives a good overview of permissions
http://codex.wordpress.org/Changing_File_Permissions
edit p.s. to access then from other networks all you will have to do is forward ports from your router to your internal server then your ftp and www services will be accessable from the outside world. I would suggest using a .htpass htaccess password to protect your services at this point.
I have first installed my WAMP Server on my personnal PC. It worked fine.
Then I pluged that PC in a network of a company (25 PC in total). I had acces to all there network. And I managed to make it work and accessible to everyone in the company but the WAMP is still on my computer.
To resolve that little problem, they got a Server with Windows Server 2012 installed. So I wanted to install my WAMP + DB, on this server.
So I installed correctly WAMP and MySql but when I go to the url that I put exactly the same on my personal PC, it shows me an error like : HTTP Error 404.0 - Not Found
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.
Like if the WAMP wasn't launched but I'm sure it is launched correctly.
Can this be a firewall issue ? Like an service bloking the port 80 (I guess ?).
Sorry but the network isn't my best subject.
EDIT
I found from where my error comes.
When I go to my url 10.13.48.60:80/my_page.php
In my error message, I see Physical Path C:\inetpub\wwwroot\
but thats wrong, it should just be Physical Path C:\WAMP\www\
How can I change that ?
I am trying to connect to a website which is hosted locally on a server but unable to connect. I have reset the IIS and try to connect it using local host but its is not working. I haven't change any thing and able to connect through it yesterday.
Can some please help and tell me what to do and what are the possibilities that why I am not able to connect.
Try to check three things.
If you are using a local host name check that, the same bindning is set on your site and that the same host name row exists in your hosts file (usually in C:\Windows\System32\Drivers\etc\hosts) like this example:
127.0.0.1 localsite.dev
Check that the sites root is pointing to the correct directory on your local machine.
If you have access to a local development tool, like Visual studio, try to compile and see if build errors exists.