search

ptrumpis / snap-camera-server

An alternative, self-hosted solution that allows you to continue using Snap Camera with all Snapchat filters after its shutdown on January 25, 2023.
https://github.com/snapcamera
MIT License
321 stars 35 forks source link

Snapcamera not getting web lenses #10

Closed rauriez closed 1 year ago

rauriez commented 1 year ago

Does it work with a snapcamera clean install(from your proton drive with no previous cache)? I followed your steps. I have the server up and runnig with certificates, edited hosts file, patched exe to access web lens but the main lenses panel remains empty with a permanent loading spinner like it would without all this. On the other hand, in the local server database, I can see like two hundred something lenses. Is there any easy way to troubleshoot this?

ptrumpis commented 1 year ago

If you don't see any snap lenses at all then you probably have blocked the domain studio-app.snapchat.com in your firewall.

rauriez commented 1 year ago

Nope. Firewall is off.

PS C:\WINDOWS\system32> Get-NetFirewallProfile

Name                            : Domain
Enabled                         : False
DefaultInboundAction            : NotConfigured
DefaultOutboundAction           : NotConfigured
AllowInboundRules               : NotConfigured
AllowLocalFirewallRules         : NotConfigured
AllowLocalIPsecRules            : NotConfigured
AllowUserApps                   : NotConfigured
AllowUserPorts                  : NotConfigured
AllowUnicastResponseToMulticast : NotConfigured
NotifyOnListen                  : True
EnableStealthModeForIPsec       : NotConfigured
LogFileName                     : %systemroot%\system32\LogFiles\Firewall\pfirewall.log
LogMaxSizeKilobytes             : 4096
LogAllowed                      : False
LogBlocked                      : False
LogIgnored                      : NotConfigured
DisabledInterfaceAliases        : {NotConfigured}

Name                            : Private
Enabled                         : False
DefaultInboundAction            : NotConfigured
DefaultOutboundAction           : NotConfigured
AllowInboundRules               : NotConfigured
AllowLocalFirewallRules         : NotConfigured
AllowLocalIPsecRules            : NotConfigured
AllowUserApps                   : NotConfigured
AllowUserPorts                  : NotConfigured
AllowUnicastResponseToMulticast : NotConfigured
NotifyOnListen                  : True
EnableStealthModeForIPsec       : NotConfigured
LogFileName                     : %systemroot%\system32\LogFiles\Firewall\pfirewall.log
LogMaxSizeKilobytes             : 4096
LogAllowed                      : False
LogBlocked                      : False
LogIgnored                      : NotConfigured
DisabledInterfaceAliases        : {NotConfigured}

Name                            : Public
Enabled                         : False
DefaultInboundAction            : NotConfigured
DefaultOutboundAction           : NotConfigured
AllowInboundRules               : NotConfigured
AllowLocalFirewallRules         : NotConfigured
AllowLocalIPsecRules            : NotConfigured
AllowUserApps                   : NotConfigured
AllowUserPorts                  : NotConfigured
AllowUnicastResponseToMulticast : NotConfigured
NotifyOnListen                  : True
EnableStealthModeForIPsec       : NotConfigured
LogFileName                     : %systemroot%\system32\LogFiles\Firewall\pfirewall.log
LogMaxSizeKilobytes             : 4096
LogAllowed                      : False
LogBlocked                      : False
LogIgnored                      : NotConfigured
DisabledInterfaceAliases        : {NotConfigured}

and hosts file is redirected to localhost

PS C:\WINDOWS\system32> ping studio-app.snapchat.com

Haciendo ping a studio-app.snapchat.com [127.0.0.1] con 32 bytes de datos:
Respuesta desde 127.0.0.1: bytes=32 tiempo<1m TTL=128
Respuesta desde 127.0.0.1: bytes=32 tiempo<1m TTL=128
Respuesta desde 127.0.0.1: bytes=32 tiempo<1m TTL=128
Respuesta desde 127.0.0.1: bytes=32 tiempo<1m TTL=128

Estadísticas de ping para 127.0.0.1:
    Paquetes: enviados = 4, recibidos = 4, perdidos = 0
    (0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
    Mínimo = 0ms, Máximo = 0ms, Media = 0ms
PS C:\WINDOWS\system32>
ptrumpis commented 1 year ago

Did you check Docker Desktop if all 4 services are running? There might be another application/server blocking a port.

rauriez commented 1 year ago

docker

ptrumpis commented 1 year ago

And you are not seeing any lenses at all? Did you try to search for anything? And can you visit http://localhost:80 in your browser?

If you click on snap3 you should be able to see all log entries.

rauriez commented 1 year ago

snap as you can see, no search option whatsoever. Maybe the search option only appears once the lenses are loaded

snap3-webproxy-1  | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
snap3-adminer-1   | [Wed Mar  8 20:19:58 2023] PHP 7.4.33 Development Server (http://[::]:8080) started
snap3-webproxy-1  | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
snap3-webproxy-1  | /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
snap3-webproxy-1  | 10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
snap3-webproxy-1  | 10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf differs from the packaged version
snap3-webproxy-1  | /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
snap3-webproxy-1  | 20-envsubst-on-templates.sh: Running envsubst on /etc/nginx/templates/default.conf.template to /etc/nginx/conf.d/default.conf
snap3-webproxy-1  | /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
snap3-webproxy-1  | /docker-entrypoint.sh: Configuration complete; ready for start up
snap3-webproxy-1  | 2023/03/08 20:19:58 [notice] 1#1: using the "epoll" event method
snap3-webproxy-1  | 2023/03/08 20:19:58 [notice] 1#1: nginx/1.23.3
snap3-webproxy-1  | 2023/03/08 20:19:58 [notice] 1#1: built by gcc 10.2.1 20210110 (Debian 10.2.1-6) 
snap3-webproxy-1  | 2023/03/08 20:19:58 [notice] 1#1: OS: Linux 5.15.90.1-microsoft-standard-WSL2
snap3-webproxy-1  | 2023/03/08 20:19:58 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 1048576:1048576
snap3-webproxy-1  | 2023/03/08 20:19:58 [notice] 1#1: start worker processes
snap3-webproxy-1  | 2023/03/08 20:19:58 [notice] 1#1: start worker process 33
snap3-webproxy-1  | 2023/03/08 20:19:58 [notice] 1#1: start worker process 34
snap3-webproxy-1  | 2023/03/08 20:19:58 [notice] 1#1: start worker process 35
snap3-webproxy-1  | 2023/03/08 20:19:58 [notice] 1#1: start worker process 36
snap3-webproxy-1  | 2023/03/08 20:19:58 [notice] 1#1: start worker process 37
snap3-webproxy-1  | 2023/03/08 20:19:58 [notice] 1#1: start worker process 38
snap3-webproxy-1  | 2023/03/08 20:19:58 [notice] 1#1: start worker process 39
snap3-webproxy-1  | 2023/03/08 20:19:58 [notice] 1#1: start worker process 40
snap3-mysql-1     | 2023-03-08 20:19:57+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.41-1.el7 started.
snap3-mysql-1     | 2023-03-08 20:19:57+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
snap3-mysql-1     | 2023-03-08 20:19:57+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.41-1.el7 started.
snap3-mysql-1     | '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
snap3-mysql-1     | 2023-03-08T20:19:57.876486Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
snap3-mysql-1     | 2023-03-08T20:19:57.878281Z 0 [Note] mysqld (mysqld 5.7.41) starting as process 1 ...
snap3-mysql-1     | 2023-03-08T20:19:57.883445Z 0 [Note] InnoDB: PUNCH HOLE support available
snap3-mysql-1     | 2023-03-08T20:19:57.883494Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
snap3-mysql-1     | 2023-03-08T20:19:57.883504Z 0 [Note] InnoDB: Uses event mutexes
snap3-mysql-1     | 2023-03-08T20:19:57.883513Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
snap3-mysql-1     | 2023-03-08T20:19:57.883519Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
snap3-mysql-1     | 2023-03-08T20:19:57.883524Z 0 [Note] InnoDB: Using Linux native AIO
snap3-mysql-1     | 2023-03-08T20:19:57.883819Z 0 [Note] InnoDB: Number of pools: 1
snap3-mysql-1     | 2023-03-08T20:19:57.883983Z 0 [Note] InnoDB: Using CPU crc32 instructions
snap3-mysql-1     | 2023-03-08T20:19:57.885841Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
snap3-mysql-1     | 2023-03-08T20:19:57.899938Z 0 [Note] InnoDB: Completed initialization of buffer pool
snap3-mysql-1     | 2023-03-08T20:19:57.902968Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
snap3-mysql-1     | 2023-03-08T20:19:57.914818Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
snap3-mysql-1     | 2023-03-08T20:19:57.930744Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
snap3-mysql-1     | 2023-03-08T20:19:57.930834Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
snap3-mysql-1     | 2023-03-08T20:19:57.968528Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
snap3-mysql-1     | 2023-03-08T20:19:57.969558Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
snap3-mysql-1     | 2023-03-08T20:19:57.969600Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
snap3-mysql-1     | 2023-03-08T20:19:57.971024Z 0 [Note] InnoDB: 5.7.41 started; log sequence number 15516138
snap3-mysql-1     | 2023-03-08T20:19:57.971386Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
snap3-mysql-1     | 2023-03-08T20:19:57.971751Z 0 [Note] Plugin 'FEDERATED' is disabled.
snap3-mysql-1     | 2023-03-08T20:19:57.974183Z 0 [Note] InnoDB: Buffer pool(s) load completed at 230308 20:19:57
snap3-mysql-1     | 2023-03-08T20:19:57.977571Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
snap3-mysql-1     | 2023-03-08T20:19:57.977626Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory.
snap3-mysql-1     | 2023-03-08T20:19:57.977636Z 0 [Warning] A deprecated TLS version TLSv1 is enabled. Please use TLSv1.2 or higher.
snap3-mysql-1     | 2023-03-08T20:19:57.977640Z 0 [Warning] A deprecated TLS version TLSv1.1 is enabled. Please use TLSv1.2 or higher.
snap3-mysql-1     | 2023-03-08T20:19:57.979157Z 0 [Warning] CA certificate ca.pem is self signed.
snap3-mysql-1     | 2023-03-08T20:19:57.979628Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory.
snap3-mysql-1     | 2023-03-08T20:19:57.980412Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
snap3-mysql-1     | 2023-03-08T20:19:57.980689Z 0 [Note] IPv6 is available.
snap3-mysql-1     | 2023-03-08T20:19:57.980812Z 0 [Note]   - '::' resolves to '::';
snap3-mysql-1     | 2023-03-08T20:19:57.980863Z 0 [Note] Server socket created on IP: '::'.
snap3-mysql-1     | 2023-03-08T20:19:57.984143Z 0 [Warning] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
snap3-mysql-1     | 2023-03-08T20:19:57.996830Z 0 [Note] Event Scheduler: Loaded 0 events
snap3-mysql-1     | 2023-03-08T20:19:57.997693Z 0 [Note] mysqld: ready for connections.
snap3-mysql-1     | Version: '5.7.41'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
snap3-webapp-1    | Snap Camera Server is running on port 5645
snap3-webapp-1    | Initialization delayed by 30 seconds.
snap3-webapp-1    | Ignoring invalid configuration option passed to Connection: driver. This is currently a warning, but in future versions of MySQL2, an error will be thrown if you pass an invalid configuration option to a Connection
snap3-webapp-1    | [INFO] [migration] Nothing to run
snap3-webapp-1    | [INFO] Done
snap3-webapp-1    | Database migration complete
snap3-webapp-1    | Initialization complete! 🎉

I've restarted the server just now to have a clean log. I can access localhost:80 alright. I get the docker "getting started" landing page

ptrumpis commented 1 year ago

Getting started landing page? What do you mean? That doesn't sound right...

You should see connections incomming in your logs if you visit http://localhost:80

And http://localhost:80 should look like this server listing

rauriez commented 1 year ago

yes, sorry. That was cached by the browser from docker's example container. This is what I get: localhost

ptrumpis commented 1 year ago

Do you see incoming requests in your log? Also close Snap Camera and restart the application. You should see incomming requests in your log.

If there is no incomming logs you need to check your /etc/hosts file

rauriez commented 1 year ago 
  TCP    [::1]:80               mycomputer:55650         ESTABLISHED
  TCP    [::1]:80               mycomputer:55651         ESTABLISHED
  TCP    [::1]:55650            mycomputer:http          ESTABLISHED
  TCP    [::1]:55651            mycomputer:http          ESTABLISHED

those are the only ones I found. And my hosts file as follows:

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.
#   127.0.0.1       localhost
#   ::1             localhost

# Added by Snap Camera Server Auto Config
127.0.0.1       studio-app.snapchat.com
# Added by Docker Desktop
192.168.1.52 host.docker.internal
192.168.1.52 gateway.docker.internal
# To allow the same kube context to work on the host and the container:
127.0.0.1 kubernetes.docker.internal
# End of section
ptrumpis commented 1 year ago

Do you see incoming requests in your log?

rauriez commented 1 year ago

I've tried several times but no.

snap3-webproxy-1  | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
snap3-mysql-1     | 2023-03-08 21:31:34+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.41-1.el7 started.
snap3-adminer-1   | [Wed Mar  8 21:31:35 2023] PHP 7.4.33 Development Server (http://[::]:8080) started
snap3-webproxy-1  | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
snap3-mysql-1     | 2023-03-08 21:31:35+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
snap3-webproxy-1  | /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
snap3-webproxy-1  | 10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
snap3-mysql-1     | 2023-03-08 21:31:35+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.41-1.el7 started.
snap3-webproxy-1  | 10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf differs from the packaged version
snap3-webproxy-1  | /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
snap3-mysql-1     | '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
snap3-mysql-1     | 2023-03-08T21:31:35.540839Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
snap3-webproxy-1  | 20-envsubst-on-templates.sh: Running envsubst on /etc/nginx/templates/default.conf.template to /etc/nginx/conf.d/default.conf
snap3-webproxy-1  | /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
snap3-webproxy-1  | /docker-entrypoint.sh: Configuration complete; ready for start up
snap3-webproxy-1  | 2023/03/08 21:31:36 [notice] 1#1: using the "epoll" event method
snap3-mysql-1     | 2023-03-08T21:31:35.542550Z 0 [Note] mysqld (mysqld 5.7.41) starting as process 1 ...
snap3-webproxy-1  | 2023/03/08 21:31:36 [notice] 1#1: nginx/1.23.3
snap3-mysql-1     | 2023-03-08T21:31:35.548486Z 0 [Note] InnoDB: PUNCH HOLE support available
snap3-webproxy-1  | 2023/03/08 21:31:36 [notice] 1#1: built by gcc 10.2.1 20210110 (Debian 10.2.1-6) 
snap3-webproxy-1  | 2023/03/08 21:31:36 [notice] 1#1: OS: Linux 5.15.90.1-microsoft-standard-WSL2
snap3-webproxy-1  | 2023/03/08 21:31:36 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 1048576:1048576
snap3-mysql-1     | 2023-03-08T21:31:35.548555Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
snap3-mysql-1     | 2023-03-08T21:31:35.548564Z 0 [Note] InnoDB: Uses event mutexes
snap3-mysql-1     | 2023-03-08T21:31:35.548569Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
snap3-webproxy-1  | 2023/03/08 21:31:36 [notice] 1#1: start worker processes
snap3-webproxy-1  | 2023/03/08 21:31:36 [notice] 1#1: start worker process 33
snap3-webproxy-1  | 2023/03/08 21:31:36 [notice] 1#1: start worker process 34
snap3-mysql-1     | 2023-03-08T21:31:35.548574Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
snap3-mysql-1     | 2023-03-08T21:31:35.548579Z 0 [Note] InnoDB: Using Linux native AIO
snap3-mysql-1     | 2023-03-08T21:31:35.548930Z 0 [Note] InnoDB: Number of pools: 1
snap3-mysql-1     | 2023-03-08T21:31:35.549198Z 0 [Note] InnoDB: Using CPU crc32 instructions
snap3-webproxy-1  | 2023/03/08 21:31:36 [notice] 1#1: start worker process 35
snap3-webproxy-1  | 2023/03/08 21:31:36 [notice] 1#1: start worker process 36
snap3-webproxy-1  | 2023/03/08 21:31:36 [notice] 1#1: start worker process 37
snap3-mysql-1     | 2023-03-08T21:31:35.552261Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
snap3-webproxy-1  | 2023/03/08 21:31:36 [notice] 1#1: start worker process 38
snap3-mysql-1     | 2023-03-08T21:31:35.578706Z 0 [Note] InnoDB: Completed initialization of buffer pool
snap3-mysql-1     | 2023-03-08T21:31:35.584954Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
snap3-webproxy-1  | 2023/03/08 21:31:36 [notice] 1#1: start worker process 39
snap3-webproxy-1  | 2023/03/08 21:31:36 [notice] 1#1: start worker process 40
snap3-mysql-1     | 2023-03-08T21:31:35.597220Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
snap3-mysql-1     | 2023-03-08T21:31:35.615502Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
snap3-mysql-1     | 2023-03-08T21:31:35.615615Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
snap3-mysql-1     | 2023-03-08T21:31:35.692145Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
snap3-mysql-1     | 2023-03-08T21:31:35.692824Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
snap3-mysql-1     | 2023-03-08T21:31:35.692855Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
snap3-mysql-1     | 2023-03-08T21:31:35.693839Z 0 [Note] InnoDB: 5.7.41 started; log sequence number 15711950
snap3-mysql-1     | 2023-03-08T21:31:35.694220Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
snap3-mysql-1     | 2023-03-08T21:31:35.694517Z 0 [Note] Plugin 'FEDERATED' is disabled.
snap3-mysql-1     | 2023-03-08T21:31:35.696655Z 0 [Note] InnoDB: Buffer pool(s) load completed at 230308 21:31:35
snap3-mysql-1     | 2023-03-08T21:31:35.700784Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
snap3-mysql-1     | 2023-03-08T21:31:35.700831Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory.
snap3-mysql-1     | 2023-03-08T21:31:35.700839Z 0 [Warning] A deprecated TLS version TLSv1 is enabled. Please use TLSv1.2 or higher.
snap3-mysql-1     | 2023-03-08T21:31:35.700842Z 0 [Warning] A deprecated TLS version TLSv1.1 is enabled. Please use TLSv1.2 or higher.
snap3-mysql-1     | 2023-03-08T21:31:35.701575Z 0 [Warning] CA certificate ca.pem is self signed.
snap3-mysql-1     | 2023-03-08T21:31:35.701650Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory.
snap3-mysql-1     | 2023-03-08T21:31:35.702012Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
snap3-mysql-1     | 2023-03-08T21:31:35.702072Z 0 [Note] IPv6 is available.
snap3-mysql-1     | 2023-03-08T21:31:35.702089Z 0 [Note]   - '::' resolves to '::';
snap3-mysql-1     | 2023-03-08T21:31:35.702111Z 0 [Note] Server socket created on IP: '::'.
snap3-mysql-1     | 2023-03-08T21:31:35.707195Z 0 [Warning] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
snap3-mysql-1     | 2023-03-08T21:31:35.716500Z 0 [Note] Event Scheduler: Loaded 0 events
snap3-mysql-1     | 2023-03-08T21:31:35.716787Z 0 [Note] mysqld: ready for connections.
snap3-mysql-1     | Version: '5.7.41'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
snap3-webapp-1    | Snap Camera Server is running on port 5645
snap3-webapp-1    | Initialization delayed by 30 seconds.
snap3-webapp-1    | Ignoring invalid configuration option passed to Connection: driver. This is currently a warning, but in future versions of MySQL2, an error will be thrown if you pass an invalid configuration option to a Connection
snap3-webapp-1    | [INFO] [migration] Nothing to run
snap3-webapp-1    | [INFO] Done
snap3-webapp-1    | Database migration complete
snap3-webapp-1    | Initialization complete! 🎉

This is all I get after restarting snapcamera. I guess I should see some here right?

ptrumpis commented 1 year ago

Yes, the connection between Snap Camera and your Server is not working.

A firewall or a similar security application could block the access. Your hosts file looks ok.

A system restart might also resolve the problem.

Also make sure calling https://localhost:443/vc/v1 in your browser returns:

{}
rauriez commented 1 year ago

Ok. It might be a docker issue. I'll look into it and get back to you tomorrow. Thanks for your help!

ptrumpis commented 1 year ago

Also check your application Log file, it should contain information about failed connections:

%USERPROFILE%\AppData\Local\Snap\Snap Camera\Log.txt
rauriez commented 1 year ago

I've got it sorted out. Problem was with an existing self-signed localhost certificate from VMware Workstation (also installed on my machine). Snapcamera application kept refusing handshake because of that. That certificate didn't show up in the management console. Disabling VMware server sharing did the trick. After that, Docker crapped out on me for some reason. Had to reinstall. Now I see those incoming requests.

incoming snap

It works:) Nice job you've done here. Thanks a lot.