Hi Michele!
It is possible, however, I don't think it can be done easily via the
ansible-openwisp2 role because the port is not configurable:
https://github.com/openwisp/ansible-openwisp2/blob/master/templates/nginx/site-conf.j2#L12-L13
So you would have to do this change on your own.
Changing
At the moment what you can do is choose a /31.
I created a couple of issues which should make this use case possible:
https://github.com/openwisp/openwisp-controller/issues/842
https://github.com/openwisp/openwisp-controller/issues/843
I hope this is better than nothing.
F.
On Thu, 14 Mar
Hi,
Is it possible to run OpenWisp with Let's on ports other than 80 and 443?
Best regards,
Michele
--
You received this message because you are subscribed to the Google Groups
"OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Actually same idea came to my mind . But i abandoned it as it populates
with a lot of subnets and makes managing them a mess. Instead of avoiding
mistakes one may create mistake due to too many subnets generated (one per
ip per device) son 20 devices allready 20 subnets.
And yes it cannot
You can try instructing the rule to create very small subnets (eg: /32 or
/31) and get 1 IP.
I remember there was an issue with subnets sized /32 which would not allow
to get 1 IP but I don't remember if this bug is still there.
Let me know if you try and if the bug is still there we should open
