Can't access localhost in LAMP [closed] - linux

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
First of all, I'm beginner at this, so don't be too harsh.
Yesterday, I wanted to make Linux Server. Installed LAMP, PhpMyAdmin. Man the websites IP static. I installed moodle on my website server. Then I closed VirtualBox and went to sleep.
Today when I runned my server and tried to access /phpmyadmin or (ipaddress)/moodle it says that webpage isn't available. Does this mean I have to do everything from the scratch again?
I'd appreciate any help.
I tried command sudo service apache2 start , but nothing changes.

Run this command in Terminal:
sudo service apache2 restart
OR
sudo restart apache2
Try the Answer on this Post

There are a lot of basic troubleshooting steps to take here.
You mentioned "localhost" in your question, but this doesn't sound like the local host; if you're connecting to your guest machine from the host machine then both machines will treat it as a networking connection (because it is networking). How that networking is configured will depend on your VirtualBox configuration.
Are you sure the virtual machine is running, the IP address is assigned, and networking is, well, working? Try pinging the virtual/guest machine from the host machine. After pausing and resuming, one of my Debian machines used to always pick up a DHCP address on the host-networking adapter despite being set to a static address in /etc/network/interfaces. Look at ifconfig to verify the IP address listed is what you expect.
Are you sure Apache is running? Try accessing it from within the guest machine on http://localhost -- by telnet to port 80, command-line tool, or full-on web browser.
Are other services working? Try to connect remotely to whatever you have running: SSH, FTP, IMAP, MySQL, NTP -- try to connect and see if the problem is the network or the service.

Related

Windows 10 to Centos7 Remote Desktop [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
My desktop computer is running Windows 10. I have created a virtual computer using Oracle VM Virtual Box that runs Centos7. In my Virtual Box settings I have changed the network adapter to Bridged Adapter. Everything starts correctly when the vm comes up. I then installed xrdp and tigervnc-server through epel. I have both xrdp and tigervnc services running. However when I try to remote desktop from Windows 10 to my virtual box, it can not connect. I can open a cmd window on Windows 10 and ping my ip address. The only thing that sticks out to me is that when I tried to enable the xrdp service, it states that it is not a native service. It still starts and attaches to port 3390. I changed this from 3389 after reading some tickets on stackoverflow.
xrdp.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig xrdp on
Is this the firewall biting me? What did I miss?
TIA
Ok, so it was the firewall that was biting me along with VM Virtual Box. In order to do remote desktop to a vm in Virtual Box, you must download an install VM Virtual Box extension pack. That will allow you to enable rdp under the display tab in settings. I also had to add the following to the CentOs firewall
firewall-cmd --permanent --add-port 3389/tcp
firewall-cmd --permanent --add-port 3350/tcp
Finally, I had to make sure that my vncpasswd was set to the same value as my CentOs login password. Otherwise it would not allow me to log in.

Raspberry Pi - suddenly no SSH access [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
Today I've noticed I can't connect to my raspi anymore using SSH with "Connection refused" or "...actively refused". It's extremely strange as far as until now, for a long time there was no problem accessing it through SSH. My raspi is actually running on wifi, I can ping it, I can HTTP access it, all the services seem to be running (I've got a streaming server on, PHP, apache, mysql - everything ok). I also have several config scripts reachable by HTTP requests, which are working normally. I have created a new set of ssh keys using
sudo dpkg-reconfigure ssh-server
then disabled and enabled ssh again via raspi-config, but nothing seems to work. Strange thing I've also noticed, that overnight, my router appended another IP address to my pi for some reason (despite that my IP lease time is set to forever on my wifi router), but I have no clue how this could affect my SSH access (maybe someone has some idea...?).
Important thing of this case is, that even if I try to locally (hdmi, keyboard, mouse) execute
ssh pi#raspberrypi
I still get "connection refused on port 22", I have no firewall and no other security stuff enabled and my router is set to forward SSH.
Actually, I can only access my raspi locally, not via network. I'm completely stuck. Any ideas? Tks.
On some systems the package ssh-server is called openssh-server.
sudo apt-get purge openssh-server
uninstall with purge, and:
sudo apt-get install openssh-server
The purge is to remove config files that may be broke.

configure virtualbox vms to use proxy settings of host [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I have about 6 VMs for testing purpose in Virtualbox. We have a proxy at work and I do not have a proxy at home. so I switch the settings now and then to get internet inside the VMs. But there has to be a way that the VMs adapt the system settings of my host, or am I wrong? Google didn't help quite good yet. I just found an article about a Microsoft loop back interface, but nothing for Linux. By the way I use Linux just since October, so I am fairly new with this operation system
Some system details:
Host:
arch-Linux with gnome shell and virtualbox 5.0.12
Guests:
Ubuntu, win7, win8, centos6 with nat bridge for internet purpose and host-only adapter for internal network
Anybody experience in the matter who can help me?
I had the same problems you had. I wanted to configure VM's over a corporate proxy. Googling did not help me either. After lots of trials and errors, i finally managed to connect to the internet.
What i did is to configure proxy settings in Guest OS.
I am using ubuntu as Guest OS and its easy to configure the proxy settings as follows:
sudo gedit /etc/apt/apt.conf
It opens the following file:
Acquire::http::Proxy "http://username:pass#myProxyAddress:port/";
Acquire::https::Proxy "https://username:pass#myProxyAddress:port/";
Acquire::ftp::Proxy "ftp://username:pass#myProxyAddress:port/";
Acquire::socks::Proxy "socks://username:pass#myProxyAddress:port/";
And you should change the username, pass, myProxyAddress and port with your own information. It should be good to go. Some apps like FireFox may still not be able to work so you can configure them manually.
I have done this in Ubuntu but it theoretically work for all linux systems. I don't how to configure system wide proxy for windows or would it solve the problem but it should also work for it.
Hope it helps.
ps: Virtual Host Adapter was blocking my Host OS (Windows). You can either bridge or disable the network adapter so that Host and Guest OS can connect to the internet.
You can try this. I tested it on CentOS with NAT model.
192.168.217.1 is gateway address, and port is proxy port in host.
export ALL_PROXY=http://192.168.217.1:port
Please check you have allow LAN connection to your proxy.

Connecting WinSCP with Ubuntu on VirtualBox [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I'm trying to connect Winscp with virtual machine. I'm working on Windows,and this problem is killing me for 5 hours. Studied a lot of examples, but I can't find out what is the problem. I tried to connect with putty to, but connection is every time refused. Tried to connect with every protocol, but didn't help. I even can't install ssh into Ubuntu, because something is blocking but not firewall(failed to fetch us archive ubuntu com). Port forwarding too wasn't very helpful.
1st Adapter is NAT, and second host-only.
Problem is that I need to enter home directory, and add some files, so I'm trying to find the easiest way to do this.
I would really appreciate any help. Here is my ifconfig, ip a, and interfaces picture.
1
Thanks!
Use the following step to configure.
1- Run ipconfig /all on your windows machine and see which ip are assigned to your virtual adopters.
2- Assign the same range ip to your virtual machine. For example:
If on virtual adopter ip is: 192.168.130.1
Then assign ip to your vm as: 192.168.130.*
and set gateway to : 192.168.130.1
and restart the service network and check the reachability by pinging from both side.
3- If You able to ping then you will be able to use internate on your VM. Then install the ssh.
Now you will be able to use.

I messed up setting up a ufw firewall on Ubuntu and can no longer log in to my server [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
Alright, so I'm not great (or even good) with servers, but have recently been put in charge of the task of setting them up. I have an application sitting on a VPS, here are the specs that may matter for this question...
Ubuntu 10.04
Nginx
ufw
So I was setting up my first firewall and was using UFW. I accidentally only opened up ports 80 and 443 (I was confused about setting up an SSL cert (also a new task)) and got logged out of the server. My ssh is set to try port 22 and so when I try to ssh in, it won't let me, I get this error --
ssh: connect to host xxx.xxx.xxx.xxx port 22: Operation timed out
So I tried to ssh in on one of the open ports by running this command --
ssh deployer#xxx.xxx.xxx.xxx -p443
and received this error --
ssh: connect to host xxx.xxx.xxx.xxx port 443: Connection refused
The same thing happened for trying port 80.
What do I do? I already have a live and very active application on this server. I need to be able to login and reopen port 22 for ssh or switch ssh over to another port.
Side note: sftp did not work either.
Most (if not all) VPS providers have a shell integrated in the control panel of the customer, so even if you have the sshd off you can still run commands on the server.
If not you can still also contact the hosting company and they can run commands on any of the virtual devices they are hosting.
Because your ssh server is running only on port 22 you will not be able to connect to it through port 80 (usually used for http) or port 443 (usually used for https). So there is nothing you can do from remote :(
If somehow you could upload and execute a file in your application, then to get a shell on the server is only a matter of uploading a reverse-shell. Some web applications allow the admins (I suppose you're an admin of the web application) to upload this kind of files (.php, .perl, etc.). Maybe is the case of your application. If you can't upload a file, then you probably are screwed.
Note that this isn't a good security practice. The application shouldn't allow you to upload and execute code, because if somehow an admin account is compromised, then the whole server may be compromised.

Resources