You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per the a part of the discussions in #3 I have been researching how to best get custom urls working in dat and on a pi behind dynamic dns because dathttpd is currently not working on my end. I have my pi set up behind my router with ports 80, 443 and 3238 forwarding to the local IP.
I have successfully been able to serve a custom dat and http url by spawning a simplehttp server at port 80 and creating a .well-known/dat file. I set an A record at my domain to point to my public IP (might change)
Per the a part of the discussions in #3 I have been researching how to best get custom urls working in dat and on a pi behind dynamic dns because dathttpd is currently not working on my end. I have my pi set up behind my router with ports 80, 443 and 3238 forwarding to the local IP.
I have successfully been able to serve a custom dat and http url by spawning a simplehttp server at port 80 and creating a .well-known/dat file. I set an A record at my domain to point to my public IP (might change)
You can access this at http://test.newcomputers.group or dat://test.newcomputers.group
The fact that I successfully got this running suggest dathttp should work and therefore configuring custom urls in the front-end should work too.
references:
https://github.com/beakerbrowser/beaker/wiki/Authenticated-Dat-URLs-and-HTTPS-to-Dat-Discovery#proposal
https://cblgh.org/host-on-dat.html
The text was updated successfully, but these errors were encountered: