help setting up Molly socket docker?

DeletedUser87

pinetree_raccoon I also use NPM as my reverse proxy. Don't forget to enable WebSocket support for Ntfy and Mollysocket btw.
If they are all in the same network, that should be fine. For allowed endpoints I would use the domain as per instructions, I don't think it takes IPs.
I don't know how your VPS is set up (I've never really used one) so I can't tell you for certain what needs to be set for MOLLY_HOST. What did you enter in NPM as the proxied IP? That's usually an IP in the CIDR of 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16. I guess the same one should be used as MOLLY_HOST. You should also be able to retrieve a 172.16.0.0/12 IP from the Docker network specifically for MOLLY_HOST, although you should be careful as these IPs are allocated dynamically and can change on container rebuilds. The example on Github lists localhost IPs (127.0.0.1, 0.0.0.0) as possible options.

pinetree_raccoon

i am completely dumbfounded.
a couple questions, not sure if they matter.
the dns provider for my domain is cloudflare. i have the A name root "mydomain.com" pointing at my public IP. i have "molly.mydomain.com" pointing at my root. should proxy status be "proxied" (orange cloud) or "DNS only" (grey cloud).

there is a environment variable "MOLLY_WEBSERVER", is this necessary to be included, true, false?

pinetree_raccoon

when i run the ping command i am still getting:

sudo docker compose run mollysocket connection ping XXXXXXXXMY_UUID_FROM_MOLLYXXXXXXXX
[2024-11-01T21:29:34Z INFO mollysocket::config] No config file supplied
[2024-11-01T21:29:34Z INFO mollysocket::vapid] VAPID public key: "XXXXXXXVAPID_FROM_COMPOSE_FILEXXXXX"
thread 'main' panicked at src/cli/connection.rs:125:28:
called Result::unwrap() on an Err value: HTTP status client error (403 Forbidden) for url (https://ntfy.mydomain.com/upiSUOMu09yU63?up=1)

when i click on "https://ntfy.mydomain.com/upiSUOMu09yU63?up=1)" from the above i get:
https://imgur.com/a/mmzv5yU

so it looks like it works? i dont know.

i think this is the crux of the issue. although i dont know exactly what that means, haha

DeletedUser87

pinetree_raccoon ohhh you're on CF, that makes things unpredictable for me.
As a general point on DNS records:
You should have one IP (since you are NPM'ing everything anyway). The A record for the second-level-domain can be whatever you want. You can set an A record for a subdomain or all subdomains with a * that will be the one for NPM.
I am not quite familiar with the "proxied" or "DNS only" status, usually there shouldn't be proxies or it will fail to connect, so I guess DNS only.
If you still get that 403 error, it obviously won't work. Check your general setup. Also test if ntfy is working at all, you can do that in the command line via curl. https://docs.ntfy.sh/publish/

pinetree_raccoon

i think i got it!?!?!?!?

i think it was the cloudflare dns settings. i had seperate CNAME's for each sub domain adn they were proxied with the "orange cloud."

i removed them all and just have two now... * and root point directly at my IP. not proxied, DNS only (grey cloud).

restarted all container and i got the unified push test notification!!

thank you so much for your help, i appreciate it. i will check back later after i have fully tested it. thank you again!!

DeletedUser87

pinetree_raccoon yep, always glad to help. Next time (for any such questions regarding hosting) don't forget to mention you're running Cloudflare. They're really not like the others with their DDoS and proxy stuff.

pinetree_raccoon

since i am new to this, i thought cloudflare was "the gold standard for dns?"
what are other people using?

DeletedUser87

pinetree_raccoon I guess they're the biggest, doesn't make them the best though. I personally can deal with the most baseline of registrars/DNS zone managers since I worked in the field and have a good understanding of how DNS and networking works. There's nothing inherently wrong with Cloudflare, they just do things differently in some areas.

TrustExecutor

DeletedUser87 Their tunnel solution is questionable regarding privacy.

I set up both ntfy and mollysocket in a virtual machine (running on the host OS without Docker), and used a separate Alpine Linux VM for a nginx reverse proxy. I used mollysocket air gapped mode. It has worked flawlessly for quite a long time now. I think the installation was pretty straight forward and I can really recommend this setup to others.

pinetree_raccoon

what is airgapped mode for?

pinetree_raccoon

just wanted to follow up in case anyone else stumbles upon this. in my docker compose for mollysocket i had to set "MOLLY_HOST=0.0.0.0"

it has been running flawless with this. AND battery life is phenomenal!

thanks all!!!

« Previous Page