Post: #1

Hello,

I have a sphereserver in a docker container ..

if I want to log in, the login attempt will show up in the log, but my login freezes ..

I have redirected in iptables.


http://prntscr.com/r1gaxx


http://prntscr.com/r1gc2f

Anyone have awareness, how does communication client <-> server?

I do not know how communication works, otherwise I would modify the iptables or the network adapter container?

After timeout client


http://prntscr.com/r1gddc

Thank you

---

if it runs on a VPS server, everything works fine.

that is, it will be something with the default gateway or forward or ... inside the container

Post: #2

En: You need to test it without any auxiliary applications. Log without a phoenix and see if you can log in.
It would take a statement from the sphere console. I think you have bad encoding. But I'm not sure.

Cz: Je potřeba to testnout bez pomocných aplikací. Loguj bez phoenixu a uvidíš, zda se Ti podaří přihlásit.
Chtělo by to výpis z konzole sphere. Domnívám se, že máš špatnou encripci. Ale nejsem si jistý.

Post: #3

Docker is a container (virtualized OS), so probably its affected in the same way as when try to run sphere behind a router/firewall, so maybe a possible fix for this is enable RestAPIPublicIP setting on sphere.ini

Clients using wrong encryption can also get stuck on login screen, so you can also check UseCrypt / UseNoCrypt settings and make sure that sphereCrypt.ini file is updated

Post: #4

(02-13-2020 02:22 PM)golfin Wrote:  En: You need to test it without any auxiliary applications. Log without a phoenix and see if you can log in.
It would take a statement from the sphere console. I think you have bad encoding. But I'm not sure.

Cz: Je potřeba to testnout bez pomocných aplikací. Loguj bez phoenixu a uvidíš, zda se Ti podaří přihlásit.
Chtělo by to výpis z konzole sphere. Domnívám se, že máš špatnou encripci. Ale nejsem si jistý.

Díky, bylo to nakonec kvůli RestAPIPublicIP.

---

(02-13-2020 02:56 PM)Coruja Wrote:  Docker is a container (virtualized OS), so probably its affected in the same way as when try to run sphere behind a router/firewall, so maybe a possible fix for this is enable RestAPIPublicIP setting on sphere.ini

Clients using wrong encryption can also get stuck on login screen, so you can also check UseCrypt / UseNoCrypt settings and make sure that sphereCrypt.ini file is updated

Thank you very much !

Problem solved RestAPIPublicIP.

I am surprised that external services are used and it is not possible to specify monitoring IP manual.

---

solved