Project

General

Profile

Bug #6148

Autoconfigbackup does not seem to function on 2.3-RELEASE and causes some aspects of GUI to become non functional

Added by Keith Milner about 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Backup/restore
Target version:
-
Start date:
04/14/2016
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.3
Affected Architecture:
amd64

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.

History

#1 Updated by Jim Pingle about 3 years ago

ACB is working here on several test systems, can you provide some more information about your hardware and pfSense configuration? Is it a full install? NanoBSD?

#2 Updated by Keith Milner about 3 years ago

Jim Pingle wrote:

ACB is working here on several test systems, can you provide some more information about your hardware and pfSense configuration? Is it a full install? NanoBSD?

Hardware is Netgate SG-4860
CPU Type is reported as:
Intel(R) Atom(TM) CPU C2558 @ 2.40GHz
Current: 1200 MHz, Max: 2400 MHz
4 CPUs: 1 package(s) x 4 core(s)

PFSense was originally the Netgate supplied image, upgraded to 2.3-RELEASE (amd64)

I have the following packages installed:
AutoConfigBackup 1.43_1
aws-wizard 0.5_1
freeradius2 1.7.3_1
ipsec-profile-wizard 0.9_1
openvpn-client-export 1.3.7_1
snort 3.2.9.1_10
System_Patches 1.1.4_1

Do you need anything else?

#3 Updated by Jim Pingle about 3 years ago

That's good enough info. I have a similar setup (except an 8860) and it's working fine here.

Can you drop us a note via referencing this ticket with your portal username, and the IP address you're connecting from? That way someone here can privately look at your account and check the server logs for you specifically to see if something else might be going on with the back end of things.

#4 Updated by Keith Milner about 3 years ago

OK, account subscription issue caused the initial failure, but the ACB module still seems to mess up the GUI if there is a login failure.

I would modify the ticket description, but it doesn't seem to let me.

#5 Updated by Jim Pingle about 3 years ago

  • Status changed from New to Resolved

I already opened a ticket for the display issue privately/internally. We'll get a fix in for that before long.

#6 Updated by Keith Milner about 3 years ago

I guess this can be closed or marked as not an issue then? I have no idea how to do that.

#7 Updated by Jim Pingle about 3 years ago

I've already marked it as Resolved, it's all set now. Thanks!

Also available in: Atom PDF