Connecting to snap server over internet #100
Replies: 3 comments 8 replies
-
|
Hm, after setting up SSL certs it seems it's probably not possible without it running on the primary domain on port 80 because of SSL shenanigans. |
Beta Was this translation helpful? Give feedback.
-
|
The snap camera application requires a HTTPS (SSL) connection to the snap server on the HTTPS default port 443. Changing the HTTPS port 443 is not possible without making additional changes to the binary with a hex editor. You might want to read through: #24 |
Beta Was this translation helpful? Give feedback.
-
|
That's definitely worth looking into. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
The hex edit worked for pointing Snap Camera at the server with no https. However, it seems like the nginx reverse proxy is not working properly. I temporarily shut down Apache and let the snap camera server run on port 80, and I'm seeing these 404s: If I point it directly at 5645 and bypass the nginx proxy it sort of works, but it doesn't load thumbnails/etc. |
Beta Was this translation helpful? Give feedback.
-
|
By the way, I changed the nginx port back to 7779, and I was able to use a shorter URL string and link directly to <myserverip>:7779 by patching FUN_1402b2440 in Ghidra; skipping the if-conditional and going straight to the inside of the if statement and replacing 0x25 (37) with my string length appeared to work. This definitely worked for using the correct link as it now appears both in the Snap Camera log and NGINX requests log, but I'm still getting 404 errors presumably from a misconfigured nginx. |
Beta Was this translation helpful? Give feedback.
-
|
This is what it looks like if I bypass nginx and point directly at :5645 by the way. Lots of errors like this in the log: |
Beta Was this translation helpful? Give feedback.
-
|
Okay, weird, I guess thumbnails are only not working on the home page, but in search they're fine...? |
Beta Was this translation helpful? Give feedback.
-
|
Seems that when searching the thumbnails come through, but once cached they no longer work. Weird. Related to NGINX? |
Beta Was this translation helpful? Give feedback.
-
|
Hardcoding <myserverip>:5645 into the proxy URL in nginx's default.conf and pointing Snap Camera.exe back at :7779 gets it to where it loads lens, but still no thumbnails, and clicking on the lens spawns a request that seems to work, but the lens doesn't actually apply. |
Beta Was this translation helpful? Give feedback.
-
|
You are probably seeing no thumbnails because you need to update the storage server url. For docker compose: For custom setups: |
Beta Was this translation helpful? Give feedback.
-
|
Making that change and adding |
Beta Was this translation helpful? Give feedback.
-
I'm running the snap server containers on a server with a public IP. There is already an Apache server on port 80, so I can't just run it there. I initially set up the server using AutoConfig.
I've configured my .env like so:
And I have a proxy in Apache redirecting a subdomain to the NGINX local port like so:
This appears to work....mostly. If I go to snap.mydomain.com in my web browser from where I'm running Snap Camera, I see the standard unconfigured nginx page:
So the request is getting through to nginx, at least.
I have the following in my /etc/hosts (Windows):
However, Snap Camera does not seem to load. The log is not terribly helpful:
I have also tried pointing directly at 5645 instead of going through the nginx web proxy. In the web browser this results in getting an empty json object
{}. No change in Snap Camera.I suspected the issue is that /etc/hosts can only define domain names to IP addresses, so I added a rewrite rule so that if someone tries to access the server IP with a URL that includes studio-app, it redirects them to the snap.mydomain.com URL.
Now if I access
studio-app.snapchat.comin my web browser I see the nginx page. Snap Camera also appears to try to connect now, but fails with SSL errors:I tried adding the certificates AutoConfig generated to the proxy, but that only seemed to make matters worse:
Any ideas for next steps? Maybe I need to get LetsEncrypt going and get a real SSL cert?
Beta Was this translation helpful? Give feedback.
All reactions