Closed uek67 closed 2 years ago
hey,
with which user are you trying to login?
Try with "uid1003" - thats da admin uid number, with the password you set before.
also you have to write your ip/hostname into the "hostname" field.
regards
Hi royrogermcfreely,
I tried with uid1003 and he password I set for the admin user but it failed:
**{
"msg": "Request was not sent! Plz check connection to server.",
"info": {
"readyState": 0,
"status": 0,
"statusText": "timeout"
}
}**
And where do I have to write the IP/Hostname in the fields???
Regards,
Uli
At the login menu, you can press the small down arrow to show more options and there you can set an Authentication Server
Do you load the client app via the container for example with http://localhost:20726/sepia/assist/tools/index.html
?
This should ensure that the server is actually reachable and set the correct hostname
automatically.
Hello fquirin and royrogermcfreely,
I changed the authentication server from home-sepia:27021 to server-ip:27201
and I load the client app via the container http://server-ip:27201/sepia/
but when I try to create in user-management with uid or email-address I get a
401 error not authorized
How to set the correct rights and how to login as admin? If anybody could help me with that.
Many thanks in advance
Uli
Your admin ID usually is uid1003
or admin@sepia.localhost
(unless you did some exotic changes to the container) and the password is whatever you've defined during the setup process as described here for example.
If you can't remember your password I suggest to simply restart the setup (maybe clean up your shared folder before).
Hi fquirin,
I made it to login with admin@spia.localhost thanks again. Now I still have to solve the problem that the client does not accept the voice input due to invalid certificates (self-signed). Let's see if I can "export" the ones of my webserver, for example - the computer on which SEPIA runs has no TLD.
Regards, Uli
Now I still have to solve the problem that the client does not accept the voice input due to invalid certificates (self-signed).
SSL certificates have been a major pain since day one for basically all my self-hosted projects :-/ When working with the SEPIA client I usually use "localhost" to avoid any issues (its regarded a safe origin) and for outside connections I use Duck-DNS + Letsencrypt (the SEPIA server has some scripts to make setup easier). How do you use the client exactly? (App, Desktop, Headless, etc.?)
Dear Community,
I need your help
I have sepia running as a docker container with nginx reverse proxy on port 20721 so far so good. I created a Admin and Assistant account with passwords , but when I try to login into the sepia web-frontend that fails , so I did without login an tried to ceate user , what fails with that error: