#Debugging daggerverse.dev
1 messages · Page 1 of 1 (latest)
if it's geo-location, it should be related with my ip
@kind meadow I get the same IP as you:
$ dig daggerverse.dev
; <<>> DiG 9.10.6 <<>> daggerverse.dev
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22465
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;daggerverse.dev. IN A
;; ANSWER SECTION:
daggerverse.dev. 352 IN A 66.241.125.177
;; Query time: 4 msec
;; SERVER: 172.19.248.1#53(172.19.248.1)
;; WHEN: Thu Nov 09 18:01:38 CST 2023
;; MSG SIZE rcvd: 60
hmm,
I'm looking for my vpn config
I'll try to change my location to USA
I switched USA based IP(157.245.244.244) and it's still working
Ahh got it
Canada based IP and this time got EOF
your module shows as loading now and I'm getting EOF from the module link
Ah, so you think it's Geo-based but at the IP level? Same IP gets routed to different machines depending on source?
no sure about geo ip yet, I'm just trying to make it work again.
not geo-ip but every time I changed IP, my target instance is chaning and didn't able to hit same instance again
Only 1 machine is running the app at the moment, so still looking into it. I'm on ground still, so can't use my laptop right now
Thanks @chrome cliff. It's not a building-on-fire emergency. Definitely frustrating, and I would like to do a retro at some point. But this is an experimental service for a reason 🙂
Appreciate the help