Project

General

Profile

Actions

Bug #6427

closed

Auto Config Backup still not working after updating to 2.3.1 R1, and reinstalling ACB

Added by Xander Venterus over 8 years ago. Updated over 8 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
Backup / Restore
Target version:
-
Start date:
05/31/2016
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:
amd64

Description

I saw that ACB was reported as resolved so i ran all updates, removed, and reinstalled ACB, well guess what its still broken.

I get a ton of these in the alerts:
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> ) @ 2016-05-31 14:27:53

My credentials have been quadruple checked, even copy pasted, and i can login to the portal as well just fine.

My subscription is only less than a month old also, so no chance of expiration.

Name pfsense.triumphcorp
System Netgate SG-4860
Serial: 1116160609
Version 2.3.1-RELEASE-p1 (amd64)
built on Wed May 25 14:56:42 CDT 2016
FreeBSD 10.3-RELEASE-p3

The system is on the latest version.
Platform pfSense
CPU Type Intel(R) Atom(TM) CPU C2558 @ 2.40GHz
4 CPUs: 1 package(s) x 4 core(s)
Hardware crypto AES-CBC,AES-XTS,AES-GCM,AES-ICM
Uptime 4 Days 22 Hours 17 Minutes 39 Seconds
Current date/time

Actions #1

Updated by Chris Buechler over 8 years ago

  • Status changed from New to Not a Bug
  • Target version deleted (2.3.1-p2)
  • Affected Version deleted (2.3.1)

it works fine, please get in touch via support for assistance.

Actions #2

Updated by Xander Venterus over 8 years ago

tolower needs to be on the username field, otherwise im sure a lot more bugs will be filed due to the username only working with lowercase spellings, even when the portal login username is setup using uppercase letters, or like ours, with a leading uppercase letter.

Actions

Also available in: Atom PDF