Hi Federico, There is an error while running postfix. Maybe that is causing trouble.
May 26 13:18:41 openwisp systemd[1]: Starting LSB: Postfix Mail Transport Agent... May 26 13:18:41 openwisp postfix[3054]: * Starting Postfix Mail Transport Agent postfix May 26 13:18:41 openwisp postmulti[3062]: warning: valid_hostname: numeric hostname: 192.168.1.143 May 26 13:18:41 openwisp postmulti[3062]: fatal: file /etc/postfix/main.cf: parameter myhostname: bad parameter value: 192.168.1.143 May 26 13:18:42 openwisp postfix[3054]: ...done. May 26 13:18:42 openwisp systemd[1]: Started LSB: Postfix Mail Transport Agent. I made changes to the /etc/postfix/main.cf file and set it same as the hostname and it worked. Regards, Nikunj On Friday, May 26, 2017 at 1:03:30 PM UTC+5:30, Federico Capoano wrote: > > Check if postfix is running correctly on the server. > > Then check the openwisp2 application logs in /opt/openwisp2/logs > (Look for the one which ends in .error.log). > > Could you tell me what you find? > > > Il ven 26 mag 2017, 09:23 Nikunj Shah <[email protected] <javascript:>> > ha scritto: > >> I cleaned up before installation. I basically uninstalled role >> openwisp.openwisp2 and ansible. >> >> Then I followed the entire procedure for fresh install, i.e. installed >> ansible, then role openwisp.openwisp2 and then the playbook command. >> >> Can you please suggest if I missed something? >> >> Regards, >> Nikunj >> >> On Friday, May 26, 2017 at 12:31:12 PM UTC+5:30, Federico Capoano wrote: >> >>> Most likely a postfix configuration issue. >>> >>> Did you update the role from galaxy before running the playbook again? >>> >>> Did you back up before upgrading? >>> >>> Federico >>> >> Il ven 26 mag 2017, 08:39 Nikunj Shah <[email protected]> ha scritto: >>> >> Hi Vivian, >>>> >>>> Can you please share some details on how you solved the User >>>> registration problem. >>>> >>>> I am facing a similar issue in latest release also >>>> >>>> Regards, >>>> Nikunj >>>> >>>> >>>> >>>> On Monday, April 10, 2017 at 9:49:27 PM UTC+5:30, Vivian Noronha wrote: >>>>> >>>>> >>>>> Hello Everyone, >>>>> >>>>> I have installed openwisp.openwisp2 using ansible-openwisp2 and this >>>>> is the response I get from the Openwisp2 when I send the registration >>>>> request. My server is located at 192.168.1.20 and clients at >>>>> 192.168.1.1/24 >>>>> >>>>> >>>>> root@lede:~# curl -s --connect-timeout 15 --max-time 30 -k -i --data >>>>> "secret=XXXXX&name=9C:65:F9:1B:63:1A&backend=netjsonconfig.OpenWrt&mac_address=9C:65:F9:1B:63:1A&key=4d46a >>>>> c046b0d8f7350b82c53c2fe6a2a" https://192.168.1.20/controller/register/ >>>>> HTTP/1.1 403 Forbidden >>>>> Server: nginx/1.4.6 (Ubuntu) >>>>> Date: Mon, 10 Apr 2017 16:04:39 GMT >>>>> Content-Type: text/plain >>>>> Transfer-Encoding: chunked >>>>> Connection: keep-alive >>>>> X-Openwisp-Controller: true >>>>> X-Frame-Options: SAMEORIGIN >>>>> >>>>> Also when i try to save the user and email field in the Users section >>>>> after initial login it gives me Internal server 500 >>>>> here is the error.log for the same: >>>>> >>>>> 2017/04/10 15:02:06 [error] 11099#0: *20 upstream prematurely closed >>>>> connection while reading response header from upstream, client: >>>>> 192.168.1.42, server: 192.168.1.20, request: "POST >>>>> /admin/openwisp_users/user/32b76742-882d-43dd-add6-19fb84059abe/change/ >>>>> HTTP/1.1", upstream: "uwsgi://127.0.0.1:3031", host: "192.168.1.20", >>>>> referrer: " >>>>> https://192.168.1.20/admin/openwisp_users/user/32b76742-882d-43dd-add6-19fb84059abe/change/ >>>>> " >>>>> 2017/04/10 15:14:57 [error] 11099#0: *49 upstream prematurely closed >>>>> connection while reading response header from upstream, client: >>>>> 192.168.1.42, server: 192.168.1.20, request: "POST >>>>> /admin/openwisp_users/user/32b76742-882d-43dd-add6-19fb84059abe/change/ >>>>> HTTP/1.1", upstream: "uwsgi://127.0.0.1:3031", host: "192.168.1.20", >>>>> referrer: " >>>>> https://192.168.1.20/admin/openwisp_users/user/32b76742-882d-43dd-add6-19fb84059abe/change/ >>>>> " >>>>> 2017/04/10 16:14:39 [error] 11099#0: *114 upstream prematurely closed >>>>> connection while reading response header from upstream, client: >>>>> 192.168.1.42, server: 192.168.1.20, request: "POST >>>>> /admin/openwisp_users/user/32b76742-882d-43dd-add6-19fb84059abe/change/ >>>>> HTTP/1.1", upstream: "uwsgi://127.0.0.1:3031", host: "192.168.1.20", >>>>> referrer: " >>>>> https://192.168.1.20/admin/openwisp_users/user/32b76742-882d-43dd-add6-19fb84059abe/change/ >>>>> " >>>>> >>>>> Best, >>>>> Vivian >>>>> >>>> -- >>>> 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 [email protected]. >>> >>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >> 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 [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
