xampp apache not running - wordpress

I want to install wordpress on localhost
I have downloaded and installed XAMPP.
I have downloaded the wordpress 3.4.1 and placed it in htdocs folder.and i renamed it as demo_folder.
when i type in navigation bar localhost/demo_folder it shows Unable to connect page.
As you can see the apache is not running as shown in fig.
when i click on start it doesnt get started
I dont know why?
can anyone help me out???
EDIT1
the below is netstat -an cmd screenshot

This is a fairly common problem with XAMPP/Windows. The usual suspect is that there is another application running on port 80, which you should terminate. Also please use the web, there is a wealth of information on this topic.
To view all currently open ports and the PID of the process using that port, open cmd and run
> netstat -o
This should help with changing the port Apache runs on: http://www.geckoandfly.com/7491/xampp-apache-wont-start-change-port-to-listen-85/ .

If you're on Windows 7, shut down the Web Deployment Agent Service. That should clear port 80.

XAMPP does have some problems with Windows. You could also try using WAMP. It seems to be a lot easier to install and use.
As for XAMPP, try making sure nothing else is using the port 80.

It seems you have tried to install the XAMP multiple times or PORT 80 has been used by other Application. If you are sure other applications is not using the Port 80 try this:
Close the XAMP and go to run and type services.msc and find the service named Apache 2.x.x etc go to its properties and get the exact name of it . For eg, mysql service name is mysql.
After you have found the service name , Open cmd with administrator privilege and type
sc delete apache
here is the manual to delete the service name :
http://technet.microsoft.com/en-us/library/cc742045(v=ws.10).aspx
after deleting the service name try opening the XAMP and click on Start next to Apache, hope it will be running now.
If nothing works above ,most of the cases I have seen Skype is the problem:
Go to Tools>Options>Advanced>Connections
Untick Use Port 80 for incoming connections

Related

Curl error 7 when installing apps on nextcloud

Hey this is my first question on here, so go easy.
I set up a Nextcloud server on my homelab in an ubuntu server 20.04 vm using the snap install. I have a seperate vm running nginx as a reverse proxy to my Nextcloud instance. Everything works flawlessly as intended, except that when I try and install apps on Nextcloud, I get a curl error #7. I've tried using my lan ip through the web ui, my public domain name through the web ui, and the commandline using the nextcloud.occ app:install command. I always get the same error. I tried to find the appropriate log file to get more information but looking in /var/snap/nextcloud/current/log/ I couldn't find any relevant info in any of the logs. Running php -m comes up with php not installed, I guess because php is installed via the Nextcloud snap? Obviously php is installed somewhere because Nextcloud is running, but I don't know how to look and see what modules are enabled, or how to install new ones using the snap. Any help on what to do is much appreciated!
enter image description here
Update: I fixed it. I think I had improperly configured my firewall, and turning it off (in proxmox)/making some changes to my /etc/netplan/*.yaml file to properly configure the static IP fixed it. GL
Another reason can be a wrongliy configured network. I forgot to set the gateway/proxy for IPv4, so github.com was unreachable. Most other services I use seem to resolve IPv6 first, so I did not have any other problems besides updating nextcloud apps.

How to connect the Atom Editor with a remote server?

I've tried looking at other questions here with similar problems, but unfortunately I haven't been able to solve this issue.
For some basic background info, I'm currently using a PC in a lab and the lab has GPU servers somewhere in the institution. I'm attempting to connect the Atom Editor to the remote host. My PC uses Windows 10 and the remote server is Ubuntu 16.04.
I've looked at thie remote-atom guide but for some reason the "Start Server" option is not working. I've also tried to do what this answer has stated, but unfortunately I don't have sudo permission.
Would there be another way that I can connect Atom remotely? Thank you.
You can easily connect to remote FTP using atom even if you do not have any sudo permission on the sudo server.
On Remote server:
- Create a rsa key (ssh-keygen -t rsa)
- add the public key to .ssh/authorized_keys file
- download the private key to you local desktop
On local machine > open Atom editor:
- press ctrl+space to open the 'ftp-remote-edit'
- add the server if not present already
Atom editor: remote server configs
That's it, you are ready to connect and edit files.
Other viable option is using VS code using winScp.

Configuring PhpStorm with Xdebug and Vagrant

I am trying to configure PhpStorm 2016.2 with Xdebug and Vagrant (Drupal VM). I have read many tutorials advising how to configure these three applications. I think it's almost there, but I'm not sure what this error is?
When I click to setup path mappings, it appears that 'File path in project' is the issue. On Vagrant I have:
/var/www/drupalvm/sitelog/index.php
On my local I have:
/Users/24ma13wg/PhpstormProjects/sitelog/index.php
...but I don't have index.php in my project files:
How can I resolve this? Thanks.
A
B
To solve the issue of needing to enable Force break at the first line when a script is outside the project can be solved by configuring PHPStorm to talk to the PHP Interpreter that is in DrupalVM.
Navigate to Preferences -> Languages and Frameworks -> PHP and click the ... next to CLI Interpreter. On the next window that pops up, click the + at the top and choose From Docker, Vagrant, VM, Remote. Choose the Vagrant Instance Folder by navigating to your local path to DrupalVM. Click OK on each of the open windows to close the options.
From here, you will just enable PHPStorm to start listening for new debug connections and will need to send a cookie along to allow to connect to xDebug.

Unable to open RStudio-server in web browser

I have installed R and Rstudio-server on Amazon AMI cloud and both are running properly as I can type R and get the R-terminal and check whether the RStudio-server is running.
sudo lsof | grep rstudio
Since Port 8787 is not accessible and there is another port something like 6970 open so I have created a rserver.conf file in /etc/rstudio/ But when I try to open RStudio server from my system's web browser I get this error
"No Data Received"
I am not sure what is the issue, any help would be greatly appreciated.
I've been using RStudio on AWS instance (EC2, Ubuntu) for several months, so I hope I can help you. First, could you clarify this part of your post?
Since Port 8787 is not accessible and there is another port something like 6970 open
I suppose you are using EC2, as it seems to be a common one for this purpose. Then, I believe you can open certain ports by configuring security groups in the AWS console (i.e. Network&Security - Security Group). Have you added a rule to allow 8787 (or 6970 if you prefer) inbound?
This worked for me.
rstudio-server online

How can i setup Drush to use a proxy server to access internet on Windows7?

i am using WAMP for Drupal development. I have installed drush and it works fine when using home network without any proxy. When i am at work, the network setting uses a proxy to access internet and hence any drush command which need internet, eg. drush dl {module_name}, doesn't work.
After googling i could only find texts that told me how to configure them on *nix based OS. I'm stuck with windows7. Any idea?
Okay. I got it running. I had to do the following change to make drush dl work on windows 7. Apparently "which wget" wasnt returning anything as windows doesn't have a 'which' command. I hacked the drush core to do the following changes.
Go to file drush.inc in folder C:\ProgramData\Drush\includes
Change the line $use_wget = drush_shell_exec('which wget'); with $use_wget = drush_shell_exec('where wget');
Root Cause:Windows doesn’t have 'which' command, 'where' command serves the purpose
I think there was no issue with proxy at all and it was using proxy from drupal's settings.php file correctly

Resources