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
Related
I commented this problem on the following thread for an active issue regarding Auth0 lock, but wanted to ask here for more reach in case anyone else has experienced this.
From what I've researched, it seems that many people are having this issue, and it doesn't seem like there's a known explanation to what's going on.
The unfortunate thing is that this is happening to end users, and from what I have seen devs have not been able to reproduce this error.
https://github.com/auth0/lock/issues/1838#issuecomment-918434321
Description
User is able to view our Auth0 Lock
User is not able to successfully sign up
We created an account for them in Auth0 directly and are able to log in using credentials we created for them via the Lock
User is not able to log in using the credentials and is shown the "We're sorry something went wrong when attempting to log in message"
Auth0 logs don't actually show this user's attempts/errors when logging in
Reproduction
Unable to reproduce locally, but trying everything we can to do so, including blocking all cookies (not the problem)
Attempting to get any console warnings from the user as well
Environment
Lock version: 11.30.4
React Version: 17.0.2
Next.js Version: 11.1.0
Chrome 91, Windows
I'd like to use expo start --tunnel to allow connecting to the App over the internet.
However, right after starting, the DevTools open and show me the following error:
Error loading DevTools
ValidationError: "urlType" must be one of [exp, http, redirect, no-protocol]
The console shows me:
Starting Metro Bundler.
Tunnel URL not found (it might not be ready yet), falling back to LAN URL.
Tunnel URL not found (it might not be ready yet), falling back to LAN URL.
So far so bad.. I've then looked into the .expo/packager-info.json to see what URLs have been generated. The file looks like this:
{
"devToolsPort": 19002,
"expoServerPort": 19000,
"packagerPort": 19001,
"packagerPid": 7316,
"expoServerNgrokUrl": "https://sz-p2a.anonymous.123.exp.direct",
"packagerNgrokUrl": "https://packager.sz-p2a.anonymous.123.exp.direct",
"ngrokPid": 5316,
"webpackServerPort": null
}
Then I've tried to open these URLs on the target devices. When doing so, I get an SSLPeerUnverifiedException because of an invalid certificate. I think it's the same error that I get when navigating to the URL directly in the browser.
So, am I doing anything wrong or is the tunnel workflow broken right now?
What might I do to get it working?
I somehow bypassed this problem by removing https from the link.
To do so, take the expoServerNgrokUrl from .expo/packager-info.json and turn:
https://sz-p2a.anonymous.123.exp.direct
into
http://sz-p2a.anonymous.123.exp.direct
Then you can send it to any Expo device.
I had the same issue, logged out expo logout, logged in again expo login and it worked.
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 have installed maximo-anywhere version 7.6.3. This is just a development environment using the simulator with mobilefirst on eclipse.
I am currently unable to login with the following message. Not authorized when logging into Maximo Anywhere - on other environments I have created I have just given the user the correct security group... however in this scenario even though I have deployed the WorkExecution application and provided the user with the ANYWHERE_TECHNICIAN security group the user is still unable to login.
Any thoughts? Has anyone come across this issue?
Login failure
This issue is related to HTTP/HTTPS. It looks like anywhere is currently unable to go over HTTPS.
The error message was just a rogue message throwing it off.
Thanks
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..