I have installed WAMP2.4 on windows 7 - 64bit. Its working fine and also i am able to connect it from localhost and from outside. Skype, IIS or VMware is not installed on the system. In
"services" the mysql and apache both are set to start automatically and are in started state. All services of WAMP is working and the icon is green.
Now, the problem is, the website goes down very often. When its down, the WAMP icon is still green, mysql and apache are still in "started" state. Then I just click on "Restart all services" every time and it starts working.
When its down, I checked the "Test port 80" of Apache>Services and it says that the port is not being used. Same time when i check port 80 with "netstat" on command prompt it show the process id of apache. If i don't do any action, after some time it start working. Is there any way to set Apache not to free the port 80? Or, any batch command which check the port 80 and if its free, restart the wamp services?
I have heard of this issue before now I come to think of it.
Try adding these 2 parameters to your httpd.conf file.
Put them after this line that should already exists in httpd.conf # EnableSendfile on
# AcceptFilter: Windows, none uses accept () instead of AcceptEx ()
# And do not recycle sockets between connections. This is useful
# Network interfaces for which the pilot is defective, and for
# Some network providers like vpn pilots or filters
# Anti-spam, anti-virus or anti-spyware.
AcceptFilter http none
AcceptFilter https none
With luck this should stop Apache from hanging, which I think is your main problem.
Related
Going around in circles. Please help, I enter http://localhost into safari on my mac and receive: It works!
However, I cannot figure out how using MySQL workbench I can find the URL. I am looking to code JSON in xCode to retrieve data from my local MySQL database, however, I do not even know the URL to access it.
My port is on 3306. I have tried http://127.0.0.1:3306 - and get a failed to open.
Do I need myphpadmin or can I go direct to MySQL?
I have tried saving a copy of MyPhPAdmin under Users>MyUserName> but this did not work when I ran: http://localhost/myphpadmin
Should the file be saved elsewhere? When I worked on Python weeks ago I run it under a different location then was recommended (Under the Python X.X cache folder) whereas online people simply ran it from their Users>MyUserName> folder. I am on the latest Catalina OS X.
Tried http://localhost/usr/local/mysql-8.0.20-macos10.15-x86_64/phpmyadmin/ - 404 not found
With MySQL, you can connect via localhost "socket" or networking "TCP/IP" connections. The user accounts in MySQL exist separately from each other, so if your user account exists with host value 'localhost' the TCP/IP connection probably won't work for you. Also note that, depending on how you installed MySQL and how it's configured, it might not even listen for network connections. Normally, localhost is preferred if you are on the same machine.
In MySQL Workbench, you need to give the hostname or IP address when selecting "Standard (TCP/IP)" from the "Connection Method" dropdown. This is simply the hostname or IP address, not a complete URL or web site. So you'd set the hostname to "127.0.0.1" or "192.168.9.34" or whatever. Again, Local Socket/Pipe is usually a better choice in most cases.
MySQL uses its own networking port (3306) and communication protocol, so using http://127.0.0.1 is incorrect as it isn't using the http protocol. Likewise, if you would need to change the port for some reason, specify that in the port field rather than as a part of the hostname.
As for phpMyAdmin, you would install that to a folder that is handled by your web server, then access it through the URL/path exposed by the web server — by default, your user home directory is not shared to the web (and rightly so, I don't want all of my documents and files shared with the world!). Put the phpMyAdmin folder in your web root and you'll have better success. Which folder that is probably depends a lot on which webserver you are running, how it is installed, and how you configured it.
I won't comment on the Python scripts you've run in the past, as my experience with serving Python to the web requires adjusting some settings in my nginx configuration and I won't want to confuse you compared to the tutorials you're following.
I'm trying to debug my PHP code running on a remote server using PhpStorm's Xdebug feature. A few weeks ago I was able to do this on another computer, but I no longer have that computer. I reinstalled and configured PhpStorm and can run SFTP and SSH with the remote server on the new computer. I tried using PuTTY, and was successfully able to use it to SSH Tunnel between the two computers and run Xdebug. But it wasn't a 'good' as the way I was able to do this on the other computer, which didn't need PuTTY.
I believe that the problem has to do with setting up Port-9000 forwarding. I added a rule for this to my BitDefender BOX2 for the local computer I develop on, but I still get refused. The tech at BitDefender thought that there may be another port that needs to be opened/forwarded in addition to port 9000.
Because the PuTTY method works on the new computer, I'm confused. Why does this work with PuTTY, but not directly with PhpStorm (without the help of PuTTY)?
Xdebug only needs port 9000, so that is the only port that PhpStorm will listen on, and Xdebug needs to connect to. I don't know BitDefender, but perhaps you only allowed outgoing connections, and not the incoming ones that you should allow?
Are the two machines on the same network, or is your machine behind a NAT network to the outside world, where your remote machine lives? In that case, you probably can't get around using your SSH tunnel with PuTTY.
You don't mention any settings, but it is worthwhile to check what shows up in the xdebug log file (when configured with xdebug.remote_log=/tmp/xdebug.log on your remote machine). It will show what Xdebug tries to connect to, and whether (and sometimes even why) the connection failed.
I can't get the Apache service to start.
When I try to start it from services I get the following events in event viewer.
The Apache service named reported the following error: (OS
10048)Only one usage of each socket address (protocol/network
address/port) is normally permitted. : AH00072: make_sock: could not
bind to address 0.0.0.0:8090
AH00451: no listening sockets available, shutting down .
AH00015: Unable to open logs
.
I've tried port 80 port 8080 and 8090 and I'm getting the same errors.
I've checked to see if these ports are in use and they are not listed through netstat or through a currports.exe I've used.
I had everything running but I did a SYMLINKS rebuild on apache and mysql and I think I may have done them too quick as I got an error message at the time and mysql and apache stayed down.
I had to re-install the mysql service but the Apache service is going nowhere!!
I have wamp 2.5 with apache 2.4.9 running on windows 2008 R2 Enterprise for the purpose of an office intranet using wordpress.
Help very much appreciated
Cheers
JCro
EDIT Code from Httd.conf. I have just added the lines I've amended #
#
Listen 12.34.56.78:80
Listen 0.0.0.0:80
Listen 80
#
# Dynamic Shared Object (DSO) Support
#
#
ServerName localhost:80
HostnameLookups Off
#
Its not too clear what caused this situation but this may get you back up and running.
Start WAMPServer
uninstall the Apache service
wampmanager -> Apache -> Service -> Remove Service
reinstall the Apache service
wampmanager -> Apache -> Service -> Install Service
start Apache
wampmanager -> Apache -> Service -> Start/Resume Service
Now if you ever want to rebuild the Apache SYMLINKS (mysql has non by default) you do this :-
wampmanager -> Apache -> Version -> (click on the current version number)
Then wait a few seconds while WAMPServer rebuilds the SYMLINKS and restarts Apache for you.
Oh then I would put Apache back to Listen on port 80.
RE: Your httpd.conf amendments
This line should be a comment, its an example but not intended to be part of the used parameters in this file
#Listen 12.34.56.78:80
These 2 lines shoud be
# this is for IPV4
Listen 0.0.0.0:80
# This is for IPV6
Listen [::0]:80
These 2 lines look ok as
ServerName localhost:80
HostnameLookups Off
How to see port number in Windows 10?
Open a command prompt window (as Administrator) From "Start\Search box" Enter "cmd" then right-click on "cmd.exe" and select "Run as Administrator"
Enter the following text then hit Enter. netstat -abno. ...
Find the Port that you are listening on under "Local Address"
Look at the process name directly under that.
After you found the PID of the service running on a given your computer, open your task Manager and sort the running processes by PID. find your target PID right click and go to services, right click on the service and stop the service. without starting your apache 2.4 service just start by getting this path "C:\Apache24\bin>httpd -k start" then enter. This is the way I become successful after many ups and down.
OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : AH00072: make_sock: could not bind to address [::]:80 (OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : AH00072: make_sock: could not bind to address 0.0.0.0:80 AH00451: no listening sockets available, shutting down AH00015: Unable to open logs
I was getting the same error when i tried to start the Apache2.4. But when i replaced the Listen 80 with Listen 8080(by going to httpd.conf file placed in conf folder inside Apache24 folder), my problem solved.
you may still get the complaint about port 443. If you look through the httpd.conf, you won’t be able to find 443. But, you will find the following:
Secure (SSL/TLS) connections
Include “conf/extra/httpd-ssl.conf”
Look in the httpd-ssl.conf file, and replace 443 with some other port.
Enjoy!
I just installed Couchbase Server 3.0.2 on Windows 8.1. The Installation went through successfully but I am unable to access http://localhost:8091/index.html.
"Google Chrome's connection attempt to localhost was rejected. The website may be down or your network may not be properly configured."
I tried to check if anything listening on that port using the command.
netstat -an -p tcp
But found nothing is listening on that port and the closest port i found was 8092, so thought may port has changed so when i try to browse on that port i got a json response as below.
{"code":404,"status":"fail","message":"controller_not_provided","ResultDate":"2015-02-06T17:13:23.2551859Z","Progress":-1,"Result":"No controller provided."}
please check the couchbase service form the windows control panel. sometimes it will not start the service automatically ,it may be manual. start the service manually , if not started then check the localhost url.
you can also start the service form the desktop icon. double click on the couchbase icon it will start the service automatically and it will open the url in your default browser.
if still facing the problem not able to start the couchbase server , follow the
.link
it describe each and every steps of the couch base installation process.
I have enabled this through windows Firewall. (I use Avast Free which doesn't have a free firewall) and I have went onto the BT router to port forward this too. Yet I still get system error 10060. I have downloaded PfPortchecker and checked port 3306 and apparently it's still not open.
I am pretty clueless on what to do here, any help is appreciated cheers.
If both MySQL Workbench and your MySQL server run on the same machine then you don't need to open any port on the modem or in the firewall. Focus on problems on your local machine.
First thing to check is: is your server actually running? Is there a service that starts the MySQL server? What setup is that? Did you install the server via the MySQL Windows Installer? If the server is running check the config file if TCP/IP networking is disabled for some weird reason (it should not, but who knows). If that is disabled you can only connect via a named pipe to your server.
Next step is to check is that the user you use to connect is actually allowed to connect from the local machine. Jeremy is right here, it matters if you use localhost or 127.0.0.1, especially if IPv6 is enabled on the box (where localhost resolves to ::1, instead of 127.0.0.1).