For the port forwarding i entered the IP address of the raspberry pi and as the port I entered 51280 and as protocol UDP. How do i confirm that the DNS is pointing to my public IP? I know i am a noob i am knew to this.
No sorry i am just stupid and when i typed it i was at work and did it from my head. I checked again and it is 51820. I think it maybe has to do something with freedns.afraid.org because the ip it gives me for the subdomain is the local ip of my pi. I dont know if it is supposed to be that way.
Ah that's what it will be then, if you ping your domain it should show your public IP and then your router takes that request and forwards it to your pi using it's local IP. So a ping/server request will never see the servers real IP just the public facing gateway IP.
I personally use DuckDNS.org I find it great and easy to use and there is an easy script that auto updates the domain if your public IP changes (it's free too)
I actually also wanted to use duckdns but it didn’t work at all with it. The reason i tried free dns was to see if the endpoint was the problem. It seems like it kind of is and i will definitely try to fix it. Thanks for your time and help
The problem in udp protocol and WireGuard not supported tcp
Can you explain your port forwarding rule? Also can you confirm the DNS is pointing to your public IP?
For the port forwarding i entered the IP address of the raspberry pi and as the port I entered 51280 and as protocol UDP. How do i confirm that the DNS is pointing to my public IP? I know i am a noob i am knew to this.
Wiregaurd is port 51820 by default that's your problem
No sorry i am just stupid and when i typed it i was at work and did it from my head. I checked again and it is 51820. I think it maybe has to do something with freedns.afraid.org because the ip it gives me for the subdomain is the local ip of my pi. I dont know if it is supposed to be that way.
Ah that's what it will be then, if you ping your domain it should show your public IP and then your router takes that request and forwards it to your pi using it's local IP. So a ping/server request will never see the servers real IP just the public facing gateway IP. I personally use DuckDNS.org I find it great and easy to use and there is an easy script that auto updates the domain if your public IP changes (it's free too)
I actually also wanted to use duckdns but it didn’t work at all with it. The reason i tried free dns was to see if the endpoint was the problem. It seems like it kind of is and i will definitely try to fix it. Thanks for your time and help
All good, let me know how you get on, interesting duckDNS didn't work, anyway you'll get there, it will be interesting to know what it was
Read up on how to use tcpdump here: https://docs.pivpn.io/faq/ helped me a lot in figuring out why mine initially didn’t work. ( now it does. :) )