form 2.4.3 upgrade 2.4.4rc20180904 can't open gateway GUI
-
just now form 2.4.3 upgrade 2.4.4rc20180904 can't open gateway GUI, network normal work,just i can't visit gateway GUI.
ERR_CONNECTION_TIMED_OUT
what's matter ? how i fix it ？？
-
i can login SSH , how i do fix web gui?
and how i use cLI command for upgrade pfsense？
-
?
If you see this :
Using username "admin". Authenticating with public key "rsa-key-20152201" Passphrase for key "rsa-key-20152201": pfSense - Netgate Device ID: 20bb46ff9538c37ed87 *** Welcome to pfSense 2.4.3-RELEASE-p1 (amd64) on pfsense *** WAN (wan) -> rl0 -> v4/DHCP4: 192.168.10.11/24 LAN (lan) -> fxp0 -> v4: 192.168.1.1/24 v6: 2001:470:1f13:5b0:2::1/64 PORTAL (opt1) -> sis0 -> v4: 192.168.2.1/24 HENETV6 (opt2) -> gif0 -> v6: 2001:474:1f13:5c0::2/128 VPN (opt3) -> ovpns1 -> v4: 192.168.3.1/24 v6: 2001:470:ccbc:2::1/64 0) Logout (SSH only) 9) pfTop 1) Assign Interfaces 10) Filter Logs 2) Set interface(s) IP address 11) Restart webConfigurator 3) Reset webConfigurator password 12) PHP shell + pfSense tools 4) Reset to factory defaults 13) Update from console 5) Reboot system 14) Disable Secure Shell (sshd) 6) Halt system 15) Restore recent configuration 7) Ping host 16) Restart PHP-FPM 8) Shell Enter an option:You'll see your two answers, right ?! ;)
-
-
Without any details to think about, I advise you use use a stable version : 2.4.3_1 - that one works great.
-
where i can find the log ?
-
What log ?
Status => System Logs => System General ?! -
i want to know why the web GUI can't open. i can login ssh.
-
Ask if the GUI web server is running well ?!
For example :
ps ax | grep 'nginx'Can you show us an image like I did above ?
Btw : if pfSense doesn't work right away you have very special hardware, or other "non-common" issues.
Use no VM - take an old 5 $ PC with a second LAN and install pfSense. That will work right away.
If still not, it's time to stop using phrases with no details, start to details what you do, how, with what etc.
Your descriptions will make s give you the answers ... -
@gertjan i only do upgrade PF 2.4.3 to 2.4.4 and then just can't login GUI. if use PF2.4.3 is work.
[2.4.4-DEVELOPMENT][admin@face.net]/root: ps ax | grep 'nginx' 322 - I 0:04.12 php-fpm: pool nginx (php-fpm) 323 - I 0:02.06 php-fpm: pool nginx (php-fpm) 45489 - I 0:08.04 php-fpm: pool nginx (php-fpm) 85193 - I 0:02.29 php-fpm: pool nginx (php-fpm) 91078 - I 0:03.10 php-fpm: pool nginx (php-fpm) 92528 1 S+ 0:00.00 grep nginx -
@yon-0 said in form 2.4.3 upgrade 2.4.4rc20180904 can't open gateway GUI:
ps ax | grep 'nginx'
It should return :
[2.4.3-RELEASE][admin@pfsense.brit-hotel-fumel.net]/root: ps ax | grep 'nginx' 22757 - Is 0:00.00 nginx: master process /usr/local/sbin/nginx -c /var/etc/nginx-webConfigurator.conf (nginx) 22913 - I 3:04.88 php-fpm: pool nginx (php-fpm) 23003 - I 0:01.45 nginx: worker process (nginx) 23349 - I 0:03.05 nginx: worker process (nginx) 24125 - Is 0:00.01 nginx: master process /usr/local/sbin/nginx -c /var/etc/nginx-cpzone1-CaptivePortal.conf (nginx) 24242 - I 0:00.03 nginx: worker process (nginx) 24477 - I 0:02.30 nginx: worker process (nginx) 24582 - I 0:00.02 nginx: worker process (nginx) 24601 - I 0:00.08 nginx: worker process (nginx) 24770 - I 0:00.03 nginx: worker process (nginx) 25031 - I 0:00.25 nginx: worker process (nginx) 25191 - Is 0:00.01 nginx: master process /usr/local/sbin/nginx -c /var/etc/nginx-cpzone1-CaptivePortal-SSL.conf (nginx) 25407 - I 0:00.08 nginx: worker process (nginx) 25596 - I 0:00.02 nginx: worker process (nginx) 25777 - I 0:01.85 nginx: worker process (nginx) 25945 - I 0:00.03 nginx: worker process (nginx) 26088 - I 0:01.96 nginx: worker process (nginx) 26229 - I 0:53.14 nginx: worker process (nginx) 34139 - I 0:20.61 php-fpm: pool nginx (php-fpm) 48058 - I 3:13.92 php-fpm: pool nginx (php-fpm) 66146 - I 2:06.93 php-fpm: pool nginx (php-fpm) 73449 - I 3:15.23 php-fpm: pool nginx (php-fpm) 81157 - I 0:45.42 php-fpm: pool nginx (php-fpm) 89990 - I 1:43.50 php-fpm: pool nginx (php-fpm)If 2.4.4 is based on the web server nginx ....
From what I read on the forum, the upcoming 2.4.4 IS pretty stable.
Check out the logs ( clog /var/log/system.log and others in /var/log ) to see why nginx isn't starting, or go back to 2.4.3_1 -
i have no find the clog / folder
find the
/var/log/system.log show:l as up/active. (Group: dn42v6)
Sep 12 02:54:28 face php-fpm[45489]: /rc.filter_configure_sync: GATEWAYS: Group dn42v6 did not have any gateways up on tier 1!
Sep 12 02:54:28 face php-fpm[45489]: /rc.filter_configure_sync: Gateways status could not be determined, considering all as up/active. (Group: dn42v4)
Sep 12 02:54:28 face php-fpm[45489]: /rc.filter_configure_sync: GATEWAYS: Group dn42v4 did not have any gateways up on tier 1!
Sep 12 02:54:30 face xinetd[87501]: Starting reconfiguration
Sep 12 02:54:30 face xinetd[87501]: Swapping defaults
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19000-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19003-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19005-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19006-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19007-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19008-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19009-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19010-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19011-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19012-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19001-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19004-udp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19013-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19014-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19015-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19002-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19005-udp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19006-udp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19012-udp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19016-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19017-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19018-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19018-udp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19019-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19020-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19021-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19022-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19023-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19024-tcp
Sep 12 02:54:30 face xinetd[87501]: readjusting service 19025-tcp
Sep 12 02:54:30 face xinetd[87501]: Reconfigured: new=0 old=30 dropped=0 (services)
Sep 12 02:54:30 face php-fpm[322]: /rc.filter_configure_sync: Gateways status could not be determined, considering all as up/active. (Group: dn42v4)
Sep 12 02:54:30 face php-fpm[322]: /rc.filter_configure_sync: GATEWAYS: Group dn42v4 did not have any gateways up on tier 1!
Sep 11 21:26:17 face php-cgi: rc.bootup: The command '/usr/local/sbin/nginx -c /var/etc/nginx-webConfigurator.conf' returned exit code '1', the output was 'nginx: [emerg] invalid port in resolver "2a05:dfc7:5::53" in /var/etc/nginx-webConfigurator.conf:42'
Sep 11 21:26:17 face kernel: done.Sep 11 21:20:03 face pkg: nginx reinstalled: 1.14.0_6,2 -> 1.14.0_6,2
Sep 11 21:20:03 face pkg: mtr-nox11 reinstalled: 0.92 -> 0.92
Sep 11 21:20:03 face pkg: mpd5 reinstalled: 5.8_7 -> 5.8_7
Sep 11 21:20:03 face pkg: mobile-broadband-provider-info reinstalled: 20170310 -> 20170310
Sep 11 21:20:03 face pkg: miniupnpd reinstalled: 2.0.20180503,1 -> 2.0.20180503,1 -
There you go :
@yon-0 said in form 2.4.3 upgrade 2.4.4rc20180904 can't open gateway GUI:
1 21:26:17 face php-cgi: rc.bootup: The command '/usr/local/sbin/nginx -c /var/etc/nginx-webConfigurator.conf' returned exit code '1', the output was 'nginx: [emerg] invalid port in resolver "2a05:dfc7:5::53" in /var/etc/nginx-webConfigurator.conf:42'
What I make of it :
nginx is not happy - see also the config file /var/etc/nginx-webConfigurator.conf - line 42Because : see the line before nfinx complaing : some gateway issue.
Because : I presume some interface trouble.What is this : "mobile-broadband-provider-info" ?
-
@gertjan
What I make of it :
nginx is not happy - see also the config file /var/etc/nginx-webConfigurator.conf - line 42resolver 202.141.162.123 2a05:dfc7:5::53 2001:19f0:7402:d:5400:00ff:fe2a:7fb6 1.1.1.1 2001:41d0:8:be92::1 valid=300s;
-
@yon-0 said in form 2.4.3 upgrade 2.4.4rc20180904 can't open gateway GUI:
resolver 202.141.162.123 2a05:dfc7:5::53 2001:19f0:7402:d:5400:00ff:fe2a:7fb6 1.1.1.1 2001:41d0:8:be92::1 valid=300s;
Really ?
This line just can't be in this file : /var/etc/nginx-webConfigurator.conf
I checked the code where /var/etc/nginx-webConfigurator.conf is build, and no way a
resolver 202.141.162.123 2a05:dfc7:5::53 2001:19f0:7402:d:5400:00ff:fe2a:7fb6 1.1.1.1 2001:41d0:8:be92::1 valid=300s;
is injected.Check line 1444 and further along in /etc/inc/system.inc.
Use option 11 ( Restart webConfigurator) or even option 1) Re asign the interfaces to make a clean start.
edit : show the /var/etc/nginx-webConfigurator.conf file please.
If the file is hosed, consider the disk in bad shape, or worse.No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ?? -
@Gertjan
I guess yon-0 is the new account of https://forum.netgate.com/user/yon in that case be prepared to spend a lotof time here.
-
i try edit the /cf/conf/config.xml and /var/etc/nginx-webConfigurator.conf file, deleted the 2a05:dfc7:5::53 and dn42 gateway, still not work. maybe i should try reset config and import again ?
-
what's mean? so old pfsense forum site close and i am come here.
-
@yon-0 said in form 2.4.3 upgrade 2.4.4rc20180904 can't open gateway GUI:
what's mean? so old pfsense forum site close and i am come here.
What he meant to say is :
You missed the mail and thousands of messages on this new forum telling that pfSense has a new forum.
https://www.netgate.com/blog/introducing-the-netgate-forum.htmlYour 'original' account still exists ... we were all forced to make a new password, that it. No need to create an new account.
@Grimson : Ohhh, yes : https://forum.netgate.com/user/yon was even discussing with @doktornotor (I actually miss him ^^) in the old days ... I'll save the link for later reading - having some fun.
-
well.., i never seen that news and i had some time no visit old forum. so i have to creat new account when i come the new forum.
