I have a Raspberry Pi running raspbian that I can no longer login to. I have been using the "pi" user without any problems up to this point. However, when it asks for a login and I input "pi", I get an error that says "Login Incorrect" and am asked for a login again. This happens at the command line as I was working on setting it up as a headless file server.
This doesn't happen if I give it the username "root". If I try to login as "root", it asks for a password but no password seems to work. I tried looking up the default "root" password and found that the "root" user is not enabled on the pi.
Strangely, if I try to access the pi via ssh (using PuTTY), I can login as the user "pi". However, as soon as I do the connection is broken with the error: "Server unexpectedly closed network connection".
What could be happening to cause this? Do I have any way of fixing the problem if I can't login?
Some background as to what might have caused this:
I was working on setting up Deluge with it's Web UI. However, deluge doesn't have init scripts so I was following this guide to create the init scripts. My pi didn't have "systemctl" installed so I started following this guide to install "systemctl". I had a problem after editing "/boot/cmdline.txt" which caused my pi to boot into safe mode. I removed my edits and the pi booted normally again.
I don't know if any of my above attempts could have caused my login problems but essentially the only thing I was doing was trying to setup deluge when I stopped being able to login.
Login as root and type:
passwd pi
And that will allow you to set a new password for user pi. if not, re install raspbian to your SD card. Works everytime.
Hope this helps.
I'm not sure why you're not able to login but I would suggest using the Deluge client instead of the WebUI as it has more features - you can get it from here
You can find a good step-by-step tutorial of how to use Deluge with a client here
In the meantime I might be inclined to start from scratch with a fresh Wheezy install instead of wasting too much time on it..
Related
We have installed new switches, and have a 10.X network for another location that they remote into via RDWeb. Since we made the changes we have not been able to use the RDWeb but we can use the desktop RDP app.
We ran the Get-RemoteAccessHeath command and got this back
RemoteAccessHealth
We then looked at the Remote access management to see what in an error state and found the blow picture.
Remote access management error
Attempted to restart the RemoteAccess service but received an error that it is an invalidoperation.
Any advice is welcome. The users are functional but would we would like to get that RDWeb page back up and running so they can use it remote in via a phone.
Thanks,
Matt
I'm having the strangest problem with Jira.
We were in the process of setting up links between Jira and Confluence and everything seemed to be working. After a restart of the machine we had some startup issues due to disabled plugs. We resolved this by deleting the rows indicating inactive plugins in the MySql database.
Everything seemed to be working. Could log into Jira. Could log into Confluence. Could connect from each to the other using application linker widget in the upper left corner of the applications.
While trying to embed some Jira into a Confluence page a user got an error and we checked the Application links.
Application link from Jira to Confluence looks good.
Application link from Confluence to Jira looks like this.
If I log onto the host machine and try to log into Jira as http://localhost:8080 i get this very strange behavior:
http://localhost:8080 brings up my Jira log on page.
If I try to log on as userX I get a try again screen.
If I try to log on as userY I get a try again screen WITH A CAPCHA.
BOTH logons DO WORK if I try to logon from https://jira.myorg.com!!!
Really confused why I can access the application but authentication fails. Any help would be greatly appreciated.
I'm still seeing this strange behavior but I've solved the problem by changing the application url to the outward facing one (https://jira.myorg.com). At one point this didn't work (that's why we used http://localhost:8080 in the first place, jira and confluence are on the same server). It seems to not need this at this point.
We did delete and recreate the links from scratch also. This is mention as a suggestion in the documentation if you are having problems with the links.
I installed my own Jitsi instance on Ubuntu, following the docs using the official packages. That worked like a charm. But I don't want to have a completely open instance, so I followed https://github.com/jitsi/jicofo#secure-domain to require a login to create a conference.
As far as I can tell, I followed exactly the docs, but after restarting Jitsi I cannot create a conference anymore. I see the following behavior:
Private URL: I get a message, that the conference has not been started and a "I am the host" button. If I push the button, I'm asked for the credentials. Doing so I get the following error message: "Oops! Something went wrong and we couldn't connect to the conference: connection.GET_SESSION_ID_ERROR"
Public URL: Browser asks for permission to use mic and camera. Then I see the Jitsi UI but camera and mic disabled. Looks like a "waiting mode".
The original installation docs mentions some log files for debugging. I checked them, but did not found anything that would be helpful or suspicious to me.
Update: If I enter wrong credentials, I get a message that they are wrong. So obviously the checking of the credentials is working.
Any idea how to solve / debug this would be appriciated.
I had the same problem and found the error at last. My domain is like "jitsi.domain.com". I created a user:
test#domain.com
and I got an error message that the host is not activated. Only after several trials I realised that the user has to be named
test#jitsi.domain.com
When trying to run exp start --tunnel in a react-native project, I often see the warning:
22:15:31 [exp] Your URL is: exp://192.168.200.83:19000
....
22:15:31 [exp] Switched to a LAN URL because the tunnel appears to be down. Only devices in the same network can access the app. Restart with exp start --tunnel to try reconnecting.
This is a problem since none of my devices or the AVD can connect to this URL to download the project.
The problem does not seem to related to any firewall settings as it does not occur every time (just very consistently). When the error does not happen, I get a URL that I can work with that looks like:
22:44:38 [exp] Your URL is: exp://en-ux3.myexpousername.myapp.exp.direct:80
Is there something that can be done about this to get it to stop switching? What causes this switching exactly? Is there some way to get devices to be able to use this URL instead (I have an android device connected to same wifi, but seems to be unable to download the project from the LAN URL)?
** Totally new to react-native and expo, so if I am missing evidence of any common debugging steps for this kind of problem, please let me know what they may be in the comments so I can update the question.
UPDATE:
A similar question to this is addressed in the expo forums: https://forums.expo.io/t/switched-to-a-lan-url-because-the-tunnel-appears-to-be-down-only-devices-in-the-same-network-can-access-the-app-you-can-restart-the-project-to-try-reconnecting/4483.
I was having the message
Switched to a LAN URL because the tunnel appears to be down. Only devices in the same network can access the app. You can restart the project to try reconnecting.
And I've solved it closing Visual Studio (then pressing the Restart button from Expo XDE)
I am trying to load the Glassfish V3 admin console but I can't get beyond the log in screen. The credentials I am using are valid but it never makes it to the main admin screen.
Glassfish is installed on a server without an internet connection which I think may be the issue. On my local machine I have no issues at all. I think the admin console is trying to connect to the update center and that is the problem, is there some config that that be changed to stop it looking for updates?
Any ideas?
I had a similar problem, this issue may be relevant. More info here.