Loss of WBM and PLCNext Engineer Connectivity after 2019.6
I am getting loss of WBM and PLCNext Engineer after upgrade to 2019.6, I can downgrade to 2019.0.4 LTS and restore both WBM and PLCNext Engineer. I have tested this on two AXC F 2152 and can replicate this issue. Is this a know issue or Do you have a link to 2019.3 as i no longer have the firmware file saved.
The WBM is displaying the standard 502 Bad Gateway nginx/1.15.2 error.
Comments
Hi Jason,
interesting behavior, but I've never heard from that.
I've updated my AXC F 2152 now also a few times from 2019.0 and 2019.3 to 2019.6 and the WBM was always displayed...
Can you please check if you can find the following files in the nginx.conf (/etc/nginx/nginx.conf)
location /wbm {alias /var/www/plcnext/wbm;index Login.html;ssi on;expires off;add_header Cache-Control no-cache;location ~*.cgi {fastcgi_pass 127.0.0.1:9001;fastcgi_pass_header Cookie;include fastcgi.conf;}add_header X-Frame-Options SAMEORIGIN;}location /welcome {alias /var/www/plcnext/welcome;index index.html;add_header X-Frame-Options SAMEORIGIN;}location /redirect {alias /var/www/plcnext/redirect;index index.html;ssi on;add_header X-Frame-Options SAMEORIGIN;}And if so, can you find the wbm files in the folder /var/www/plcnext?
Those information are for me very interesting and could give me an indication what went wrong during the update.
I guess the final solution would be a reset to the backup image (golden image - recovery type 2) and update than once again to FW 2019.6.
Please find in the following link a short description how you can perform a recovery (type 2).
Recovery Type 2
cu
Frank
Hi
The 502 Bad Gateway nginx/1.15.2 error. comes if you upgrade/reboot the PLC and have the WBM/PLC home page showed at the same time.
If you try to reload (F5) in browser the problem will be the same.
If you enter the URL/IP of the PLC in again without https, it will reload in a new session on the plc, and then it works again.
I have seen this a couple of times the last days when i updated 4 controllers.
Yes the config file nginx.conf seems to match the snippet you posted. Also the /var/www/plcnext/WBM has lots of files and i do not have anything to compare the directory with to see if ones missing or not. I can get it working just by simply down grading firmware to 2019.0.4 LTS and both WBM and PLCNext Engineer regains connectivity. I have got the same result on two AXC F 2152 and can replicate it over and over again just by switching firmware versions. Will all that being said and am pretty certain the firm ware is corrupt but i have also downloaded new copies of FW 2019.6 and sill getting same results. I would revert back to FW 2019.3 but there is no longer a link on the website for it and i can not find where i would have saved a copy of it at..
Thank you.
Hello Jason,
to get this running do a factor one reset after updating to 2019.6.
Unfortunatly from 2019.3 -> 2019.6 some config files changed significantly and this cuases the problem you are having.
If you have installed alot of additional packages you might have to manually adapt all these changes.
If you do not have anything specific on your PLC you can simply Upgrade to 2019.6 and then do a factory reset (Type 1).
I am in a similar situation but none of the presented solutions on the forum work for me to recover.
I had previously been able to connect with the F2152 both with web interface and ssh.
I then updated time and timezone and changed admin and root password.
Next, I changed the IP address of the PLC over ssh.
After that, PLC is unreachable, even after type 1 reset.
Access via web browser gives: 502 Bad Gateway / nginx 1.12.1
Access via ssh fails both with initial password written on PLC and new password set earlier.
Even working from different PC or operating system (Windows, Linux) does not help to connect to this bricked PLC
HW version 2, FW version 19.0.0.17548, FPGA version 1.1.71, Serial no. 1361697524
----
I was able to recover from this bricked situation by doing a type 2 factory reset.