š
š
You should not need to port forward anything.
You might consider using a simple front end to iptables like UFW, Uncomplicated Firewall. Simple easy and gets the job done.
š
It is oddš that tor complained that your IP address changed. It should not do that. I would assume a VPS would have a static ip address.
š
The ip addresses are
š
IP:šš š142.4.217.95
Decimal:šš š2382682463
Hostname:šš šca3.pulseservers.com
ASN:šš š16276
ISP:šš šOVH Hosting

IP:šš š167.114.35.28
Decimal:šš š2809275164
Hostname:šš š167.114.35.28
ASN:šš š16276
ISP:šš šOVH Hosting

š
š

Message: 2
Date: Sat, 5 Dec 2015 11:18:18 -0800
From: Kurt Besig <kbesig@socal.rr.com>
To: tor-relays@lists.torproject.org
Subject: Re: [tor-relays] Unbelieveable
Message-ID: <5663387A.3010705@socal.rr.com>
Content-Type: text/plain; charset=windows-1252

šDec 05 21:17:46.000 [notice] Your IP address seems to have changed
što 167.114.35.28 (METHOD=INTERFACE). Updating. Dec 05 21:17:46.000
š[notice] Our IP Address has changed from 142.4.217.95 to
š167.114.35.28; rebuilding descriptor (source: METHOD=INTERFACE).
šDec 05 21:18:42.000 [notice] Your IP address seems to have changed
što 142.4.217.95 (METHOD=GETHOSTNAME HOSTNAME=ca3.pulseservers.com).
šUpdating. Dec 05 21:18:42.000 [notice] Our IP Address has changed
šfrom 167.114.35.28 to 142.4.217.95; rebuilding descriptor (source:
šMETHOD=GETHOSTNAME HOSTNAME=ca3.pulseservers.com). Dec 05
š21:18:43.000 [notice] Self-testing indicates your ORPort is
šreachable from the outside. Excellent. Publishing server
šdescriptor. Dec 05 21:38:37.000 [warn] Your server
š(142.4.217.95:9030) has not managed to confirm that its DirPort is
šreachable. Please check your firewalls, ports, address, /etc/hosts
šfile, etc. Dec 05 21:58:37.000 [warn] Your server
š(142.4.217.95:9030) has not managed to confirm that its DirPort is
šreachable. Please check your firewalls, ports, address, /etc/hosts
šfile, etc.

I've gotten this far, not being much good at networking I can't tell
where the problem lies.. do I need to forward something?

š