I have a Wordpress website running in a Lightsail instance. I am using Bitnami, and something weird happened.
I was running some script to renew my certificate and suddenly my internet connection crashed. When I logged in back into my AWS Lightsail and tried to SSH again into the Wordpress instance, it get stuck on a black window.
I tried to reboot the instance and stop I and start it again but nothing, still the same issue.
After a while, while I had my SSH connection open (still in black screen) I rebooted the instance, doing this it force my black screen to show the login details and what I can see in the window, other than the Bitnami logo, is the following:
Last login: Tue Jul 13 19.58.55 2021 from my IP
could not chdir to home directory /home/bitnami: Permission Denied
/bin/bash: Permission denied
According to the screen, I was logged in all the time but I have a Permission denied issue which I believe it stops the instance from displaying any result.
Did anyone ever faced this issue and can help me to find a solution?
I read every where that they suggest to SSH from the terminal rather than the browser, but I don't have the SSH key for this instance as it get created automatically when they deployed it.
Related
I'm managing a Rails website that relies on MySQL tables. I used to be able to access the tables with Webmin by going to xxx.xxx.xxx.xxx:10000 . At some point, I lost the ability to access it this way.
I'm not great with SSH, but I was able to SSH into my website as a general user. Then, I switched to Root user. Then, I ran this command to restart my Webmin:
svcadm restart webmin
It seemed to accept the command, but I'm not really sure how to check. Anyway, I started getting a new error message when I tried to access Webmin through my browser:
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
The website uses a connection with Cloudflare. My guess was that this could be the problem since Cloudflare doesn’t support port 10000. I tried deactivating Cloudflare, but it didn't resolve the problem.
Still, I figured I might need to use SSH to change the port for Webmin access just in case. I found a source that suggested how to do it, and it starts with SSH. I went in through SSH and I switched to Root user. Then, I ran this command:
/etc/webmin/miniserv.conf
And it tells me
bash /etc/webmin/miniserv.conf Permission denied
How can I get past this step? Am I headed the wrong direction to get access back to Webmin? Thank you!
I have created 4 instances in two separate instance groups based on two vm templates.
Initially I was using the "SSH" button within google cloud console, and I noticed about 40% of the time would it actually work. I would often have to stop/restart the machines in order for the SSH to work. After a day or so later, the SSH button stops working. I figured this was just silly bug, and having actual SSH keys and logging in via normal SSH would work fine.
Well today I configured normal ssh keys, and I was getting the following on 3 of 4 instances:
Permission denied (publickey).
I logged into the cloud console and clicked the ssh button on all 4 instances and low and behold only 1 / 4 works.
So my question is... why am I having to keep rebooting instances just to keep my ssh working. I have never had this problem on any other cloud server before.
Note: I created a base ubuntu from their available images, and built a generic server, then used that as the base template and forked it to create the other 2 instance group templates.
I am thinking that the ssh daemon might be crashing, but how the heck can I tell, and how can I fix it?
I took the silence from the community as an indicator that the problem was only affecting myself. It turns out the stock image I had chosen to start as a base template had a buggy SSH daemon. It was a fairly quick process to rebuild my templates off of a different stock image, and since then I have had no problems connecting to my machines via ssh.
I have my website with digitalocean set up to access with ssh and webmin. i went to access it as normal, but suddenly it isn't working. safari shows the connection as refused.
usually it's my-ip:100000 to access but suddenly it's not working. i haven't changed anything so advice appreciated. thanks.
the website itself still works and is powered on.
Sorted this by running a restart through the command line using:
/etc/init.d/restart webmin
I have installed OrangeHRM 3.1.2 in live server and accessing through a domain name.
Issue I am facing is - When I am trying to loggin to the following link "http://example.com/hrm/symfony/web/index.php/auth/login" - With valid credentials. I was not logged in or neither I am not displayed with any exceptional Message, but I was able to see the URL as follows - "http://example.com/hrm/symfony/web/index.php/pim/viewMyDetails" which means I have logged in but the screen have not changed and I am still seeing the Login screen.
The Orange HRM is hosted in Godaddy Linux hosting.
I am using Windows 7.
I have checked this scenario in cross browser as well.
When I tried after few or many mins, I was able to login without any issues. As I am facing this issues frequently. I am unable to track My Staffs login and logout time exactly.
As I am not a developer, I am not sure what was the issue. Can someone please help me solving the same and just let me know if you need any more information.
Appreciate your valuable response.
Thanks,
Karthi
Please check your php session save path. Make sure it is writable by the webserver you are running , either apache or nginx or php-fpm. I had the same issue and i was able to solve giving proper permissions to the session save path directory.
My EC2 (Windows Server) instance was accessible through RDP logging in as Administrator and the default password retrieved from EC2 dashboard (AWS Management console).
I relegated my domain name to Route 53, and I also created an Elastic IP address for my instance and modified the DNS CNAME record to point to the EIP.
http access to my app works fine using domain name.
However, RDP broke since my existing rdp link pointed to the old public DNS name given to my EC2 instance.
I tried to recreate the RDP link and all the following attempts failed:
Using an RDP link downloaded from EC2 dashboard on AWS management console.
Enter the Elastic IP's public DNS name into the 'Computer' field of the RCP General tab (click on options on the bottom left of the dialog)
Enter the Elastic IP's external IP address (ie the XX.YY.ZZ.VV taken from ec2-XX-WW-ZZ-VV.compute-1.amazonaws.com ) into 'Computer' field.
Enter the EC2 Private IP address taken from the EC2 console into the 'Computer' field
In all cases listed above I used the existing password and I double checked by decoding the the Administrator's password again (from EC2 console using the original key file).
And in all cases, I keep getting the invalid credentials error from RDP connection.
For all practical purposes, I am locked out of my running instance.
HELP
Thanks...
Firstly, the first thing you should do after Creating an EC2 instance is change the Administrator password. Its easy to lock yourself out of an EC2 instance permanently by neglecting to change this. For example if you create an EBS Image and restore it you'll no longer be able to decrypt the windows password.
Are you still able to retrieve the windows password using the Management Console? If not, then the password will irretrievable. Have you tried rebooting the instance. Double check your Route 53 settings to make sure you are pointing to the correct instance and you're not trying to log into someone elses.
If all else fails I'd suggest rebuilding the instance, and immediately changing the password before changing any other settings.
I had the same problem with newly created EC2 machine: after downloading RDP file and decrypting password, RDP doesn't work. I solved it by typing public IP adress in RDP interface input box and providing same password and user Administrator. Looks like another bug in EC2...
I had the same problem. The reason is because AWS does not support saved credentials. Now I know you will say, "but I'm typing in/ copy-pasting my existing password that I have checked and re-checked with my AWS console", yes but the silly thing takes 'Administrator' as a saved credential! :D
So all you have to do is click use another account on the RDP login dialogue box and type 'Administrator' and your existing password and voila! You'll get the trusted certificate dialogue, click continue and in you get.
I was frustrated too, hope this helps. Cheers.