Open mcduffman opened 1 year ago
Hi,
Are you sure that your node web server address and port are correct, and its 'active' value is set to 'true'? as shown below
Is the directory path you set valid?
Could you please share the Docker logs for your web server(called mngr) container? You can retrieve them from Visual Studio Code using the Docker extension.
Directory path is valid for my setup.
2023-05-05 04:07:39 ROOT_DIR_PATHS: /mnt/host/d/containers/feniks 2023-05-05 04:07:39 DEEPSTACK_DT: 1 2023-05-05 04:07:39 DEEPSTACK_OD: 1 2023-05-05 04:07:39 DEEPSTACK_FR: 1 2023-05-05 04:07:39 SNAPSHOT_PROC_COUNT: 2 2023-05-05 04:07:39 RTMP_PORT_START not found 2023-05-05 04:07:39 RTMP_PORT_END not found 2023-05-05 04:07:39 READONLY_MODE not found 2023-05-05 04:07:40 [GIN-debug] [WARNING] Creating an Engine instance with the Logger and Recovery middleware already attached. 2023-05-05 04:07:40 2023-05-05 04:07:40 [GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production. 2023-05-05 04:07:40 - using env: export GIN_MODE=release 2023-05-05 04:07:40 - using code: gin.SetMode(gin.ReleaseMode) 2023-05-05 04:07:40 2023-05-05 04:07:39 2023/05/05 04:07:39 Redis host: 127.0.0.1 2023-05-05 04:07:39 2023/05/05 04:07:39 Redis port: 6379 2023-05-05 04:07:39 2023/05/05 04:07:39 Session timeout has been checked 2023-05-05 04:07:39 2023/05/05 04:07:39 MONGODB_CS: mongodb://localhost:27017 2023-05-05 04:07:39 2023/05/05 04:07:39 DirPaths: [/mnt/host/d/containers/feniks] 2023-05-05 04:07:39 2023/05/05 04:07:39 Disk Usage has checked the disk and no action has been taken 2023-05-05 04:07:40 2023/05/05 04:07:40 user count: 1 2023-05-05 04:07:40 2023/05/05 04:07:40 web server port is 8072 2023-05-05 04:07:40 2023/05/05 04:07:40 Hub integration is disabled 2023-05-05 04:08:09 2023/05/05 04:08:09 Heartbeat was beaten at Fri May 5 04:08:09 2023 2023-05-05 04:08:39 2023/05/05 04:08:39 Session timeout has been checked 2023-05-05 04:08:39 2023/05/05 04:08:39 Heartbeat was beaten at Fri May 5 04:08:39 2023 2023-05-05 04:08:39 2023/05/05 04:08:39 Disk Usage has checked the disk and no action has been taken 2023-05-05 04:09:09 2023/05/05 04:09:09 Heartbeat was beaten at Fri May 5 04:09:09 2023 2023-05-05 04:09:39 2023/05/05 04:09:39 Session timeout has been checked 2023-05-05 04:09:39 2023/05/05 04:09:39 Heartbeat was beaten at Fri May 5 04:09:39 2023 2023-05-05 04:09:39 2023/05/05 04:09:39 Disk Usage has checked the disk and no action has been taken 2023-05-05 04:10:09 2023/05/05 04:10:09 Heartbeat was beaten at Fri May 5 04:10:09 2023 2023-05-05 04:10:39 2023/05/05 04:10:39 Session timeout has been checked 2023-05-05 04:10:39 2023/05/05 04:10:39 Heartbeat was beaten at Fri May 5 04:10:39 2023 2023-05-05 04:10:39 2023/05/05 04:10:39 Disk Usage has checked the disk and no action has been taken 2023-05-05 04:11:09 2023/05/05 04:11:09 Heartbeat was beaten at Fri May 5 04:11:09 2023 2023-05-05 04:11:39 2023/05/05 04:11:39 Session timeout has been checked 2023-05-05 04:11:39 2023/05/05 04:11:39 Heartbeat was beaten at Fri May 5 04:11:39 2023 2023-05-05 04:11:39 2023/05/05 04:11:39 Disk Usage has checked the disk and no action has been taken 2023-05-05 04:12:09 2023/05/05 04:12:09 Heartbeat was beaten at Fri May 5 04:12:09 2023
The web server appears to be running fine. What operating system are you using? If you are using Windows or macOS, you won't be able to connect to the web server because those operating systems don't support the Docker network mode 'host'.
With some reconfiguring, I got into the panel. Login issue resolved.
AI service however is saying that it isnt available.
Which AI service do you use? I strongly recommend using Deepstack AI service, as shown below:
With some reconfiguring, I got into the panel. Login issue resolved.
AI service however is saying that it isnt available.
I can't log in and register either. How did you solve it?
Experiencing this as well. Very frustrating to be stuck at this login/register screen which is not mentioned in docs at all.
I have tried both "redis and mongo inside docker-compose" and outside running separate.
What is supposed to happen at this screen? Should I be registering? Is there a default password? No mention of password, admin, login etc in the documentation.
You don't need to enter the default admin password since it is automatically set. The default user credentials are Username: "admin", Password: "admin", Email: "admin@feniks.com",
Could you please share the Docker logs of your web server (called 'mngr')? This will help me identify the issue and provide a suitable solution.
With some reconfiguring, I got into the panel. Login issue resolved.
AI service however is saying that it isnt available.
Hello What configuration have you done that solved your login problem? I get the following error when logging in. Where do you think I went wrong?
My feniks settings: The directory path is valid for my setup. My node web server address and port looks correct and its "active" value is set to "true"? As shown below
my docker installed on windows.
With some reconfiguring, I got into the panel. Login issue resolved. AI service however is saying that it isnt available.
Hello What configuration have you done that solved your login problem? I get the following error when logging in. Where do you think I went wrong?
My feniks settings: The directory path is valid for my setup. My node web server address and port looks correct and its "active" value is set to "true"? As shown below my docker installed on windows.
Docker on Windows has issues with networking depending on the modes used, and as such is not recommended for use with Feniks personally. You would be MUCH better off if you were to get VirtualBox and spin up a Linux VM. From there, you can do the docker install as normal and then instead of referencing "localhost" you would simply reference the IP Address of the VM.
The particular issue stems from the fact that "The host networking driver only works on Linux hosts, and is not supported on Docker Desktop for Mac, Docker Desktop for Windows, or Docker EE for Windows Server."
https://docs.docker.com/network/network-tutorial-host/#prerequisites
Currently, I installed Docker on Almalinux and run the "Docker Compose up" command, but I still have the same problem as the previous problem to login the program and I have the same error. The following configs are from my new configuration in Docker on AlmaLinux.
[root@camera camera]# docker images REPOSITORY TAG IMAGE ID CREATED SIZE mongo latest 01e8e54fc538 4 days ago 720MB redis latest 506734eb5e71 5 days ago 138MB gokalpgoren/webapp v1.0.1-amd64 546788660fd0 4 weeks ago 145MB gokalpgoren/onvf v1.0.1-amd64 a07409dc0939 4 weeks ago 1.09GB gokalpgoren/alpr v1.0.1-amd64 f6ca63a6538a 4 weeks ago 1.11GB gokalpgoren/smcp v1.0.1-amd64 182319cb15d9 4 weeks ago 2.32GB gokalpgoren/mngr v1.0.1-amd64 697f3893186d 4 weeks ago 1.99GB gokalpgoren/face_recognition_pytorch v1.0.1-amd64 e0fcf0acefcd 4 weeks ago 6.43GB gokalpgoren/snapshot_service v1.0.1-amd64 cd63164838b6 4 weeks ago 1.23GB gokalpgoren/detect_service_pytorch v1.0.1-amd64 933d0fd4b881 4 weeks ago 7.08GB gokalpgoren/ffmpeg_service v1.0.1-amd64 44ce5e80a218 4 weeks ago 772MB gokalpgoren/openalpr_local latest bf45835171bf 16 months ago 1.2GB
[root@camera camera]# docker container ls CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES e6bbb00b370a gokalpgoren/openalpr_local "bash" 58 minutes ago Up 58 minutes lpr1 41b0e785c7eb gokalpgoren/openalpr_local "bash" 58 minutes ago Up 58 minutes lpr0
[root@camera camera]# docker network ls NETWORK ID NAME DRIVER SCOPE cfd0c94896d3 bridge bridge local 065a8007a000 camera_default bridge local 85e4cfcaf7c1 host host local 5d595a4f7f8c none null local
[root@camera camera]# ip addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether a6:2a:12:8e:3d:d7 brd ff:ff:ff:ff:ff:ff altname enp0s18 inet 192.168.101.9/24 brd 192.168.101.255 scope global dynamic noprefixroute ens18 valid_lft 274549sec preferred_lft 274549sec inet6 fe80::a42a:12ff:fe8e:3dd7/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default link/ether 02:42:35:49:e5:0b brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever inet6 fe80::42:35ff:fe49:e50b/64 scope link valid_lft forever preferred_lft forever 4: br-065a8007a000: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:90:fd:d2:cf brd ff:ff:ff:ff:ff:ff inet 172.18.0.1/16 brd 172.18.255.255 scope global br-065a8007a000 valid_lft forever preferred_lft forever inet6 fe80::42:90ff:fefd:d2cf/64 scope link valid_lft forever preferred_lft forever 14: vethdc9494a@if13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default link/ether 56:ca:6b:a4:cd:b4 brd ff:ff:ff:ff:ff:ff link-netnsid 3 inet6 fe80::54ca:6bff:fea4:cdb4/64 scope link valid_lft forever preferred_lft forever 16: veth8197412@if15: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default link/ether 3a:08:cd:31:1b:dd brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fe80::3808:cdff:fe31:1bdd/64 scope link valid_lft forever preferred_lft forever
My "docker-compose.yml" File echo :::::::::
version: '3' services: redis: image: redis container_name: redis-instance restart: unless-stopped ports:
@mahdi-yahyaie
Is the referenced Linux install bare metal, or virtual? Either way based on the response from the ip took it appears you have a network misconfiguration issue now that is hindering you.
Loopback (127.0.01) works whether or not a machine has network connectivity and no interface should ever be manually assigned a loopback address.
After deploying the docker, no login occurs. No errors are given either.
Followed the instructions exactly and used the Wizard for the docker compose file.