Recent content by s2svoip

second this, it works great

should this be done before updating Adrian ?

ok I think I got it sorted, I did not purge ip tables before my install so I think that caused an issue, but here is how I fixed nftables apt purge nftables apt-get install -y nftables cp /home/django-pbx/pbx/pbx/resources/etc/nftables.conf /etc/nftables.conf chmod 755 /etc/nftables.conf edit...

so i did another deployment on Azure this time and documented my steps, following everything I am getting a server error 500 for nftables - i put my IP in with /32 but still no dice - so I am not locked out of the deployment, but nftables it not running root@django1:~# /usr/sbin/nft list set...

thanks that helped, how do you delete that chain, i am trying nft delete chain filter trace_chain

The versatility of the nftables would always lead me to want to run it, that with the fact it’s as the system was designed. Right now I run my fusion instance with very strict firewalls and static IPs on all my clients - while I love this piece of mind I would rarther have the 20 packet white...

so i think there is more issues with nftables with this deployment type, i got an extension registered no issue, but if I reboot the box, and it clears the SIP Customer list, the T43U does not re-register, it just sits at registering - if I add my external IP to the SIP customer list, then the...

yep re-did it from the start with /32 in there and the firewall pages work

Humm, I tried adding /32 disabled and reenabled nftables and rebooting, but I still get the server 500 error. I could try and redo from the start So on a bigger picture question here, the main issue here is deploying on anything that dosent have a direct external address, if your behind NAT in...

Error: No such file or directory dosent look like it - https://prnt.sc/66qFS7MRU3ye

thanks for your testing, so i followed this and indeed was able to retain access after a reboot, one issue I am seeing is Server Error (500) when trying to access the firewall block list or whitelist - when I saw this before it was due to nftables not being enabled, but it is this time.. So...

yeah thats what I have been finding, I have a snapshot of the instance right up until I enable nftables, so ive been reverting to that - but have not figured out whats causing the issue because your either locked out, or as you say it kills it so cant get any visibility even via browser ssh

did you systemctl enable nftables ?

i would check your ext-sip-ip / ext-rtp-ip internal & external if your doing NAT to get to your box, if you are these need to be set to your external IP then reboot your system

gave this a try and no dice, same outcome it should be noted its not just connectivity with the box via http/https that is lost, you cant ssh into it either, you totally loose access - so it might be more than just nginx - more likley a nftables issue ? I also uninstalled iptables piror to...