Bug #6148
closed
Autoconfigbackup does not seem to function on 2.3-RELEASE and causes some aspects of GUI to become non functional
0%
Description
AutoConfigBackup does not seem to work correctly on v2.3-RELEASE causing errors:
Apr 14 14:07:28 ishtar check_reload_status: Syncing firewall
Apr 14 14:07:28 ishtar php-fpm93047: /firewall_rules.php: Beginning https://portal.pfsense.org configuration backup.
Apr 14 14:07:29 ishtar php-fpm93047: /firewall_rules.php: An error occurred while uploading your pfSense configuration to portal.pfsense.org (<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>401 Authorization Required</title> </head><body> <h1>Authorization Required</h1> <p>This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.</p> </body></html> ) - <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>401 Authorization Required</title> </head><body> <h1>Authorization Required</h1> <p>This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.</p> </body></html>
Apr 14 14:07:29 ishtar php-fpm93047: /firewall_rules.php: New alert found: An error occurred while uploading your pfSense configuration to portal.pfsense.org (<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>401 Authorization Required</title> </head><body> <h1>Authorization Required</h1> <p>This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.</p> </body></html> )
Note that the user credentials have been double checked and have successfully been used to log into portal.pfsense.org using a web browser. The settings were also operational prior to the upgrade.
A side effect of this is that, subsequently many of the dynamic items in the GUI stop working. This includes the Update check on the System Information dashboard widget, the IPSec widget overview and tunnel status, and the graphs in Status/monitoring. Also the "Mark All as Read" button does not clear the alerts regardless of whether the text or the wastebin icon is clicked.
These all work until a configuration change causes autoconfigbackup to fail, and then from that point onwards they stop working.
Removing the AutoConfigBackup settings and rebooting restores the GUI and any changes made without autoconfigbackup configured do not break the GUI.
Updated by 
Updated by