Security

Finished upgrading Clearpass 6.6.10 to 6.8 for a customer and after the upgrade users were receiving a "404 Error Page not found" when accessing captive portal guest self-registration page. We could not even edit the self-registration page in Clearpass Guest nor could we launch the page from the editor. What we ended up doing to get the captive portal back online was to make a duplicate of the original self-registration page and configuring the L3 Captive Portal authentication configuration to point to the new self-registration page name.

My question is has anyone come across this issue and or is there a way to fix this? The duplicated self-registration page has the original self-registration page as its parent. So we may end up creating a new self-registration page with the settings from the original page, deleting the duplicate and parent pages and renaming the new self-registration page to the original name.

The customer is using a 7030 controller running 6.5.x code with Clearpass being upgraded from 6.6.10 to 6.8.

The self-registration page was customized with customer specific photos and it was using the Galleria 1 Skin plug-in. 

In my lab I upgraded my Clearpass server from 6.6 to 6.8 and had no problems with any of my self-registration pages. I have about four of them that I use for testing and with two of them customized using the Galleria skins.

Thanks.

Hello, 

We have not seen any customer reported this issue, post the 6.8.x upgrade, we also have upgraded our lab Clearpass to 6.8.x not seen this issue, i am not sure, if this has to do with Galleria skin feature we added, The exerpt from the Clearpass release notes of 6.8.x below:

To confirm if you go to the self-reg list, select the original entry, and click Launch it gives a file not found?  Could you re-save it?  the system does serve up files differently as of 6.7, but I have never seen a problem from an upgrade.  

Yes when I go to the self-reg list and select the original entry when I click on Launch or Launch Login it gives me the 404 not found error. I can't even edit the page as when I click edit the whole browser page refreshes and nothing happens so i can't re-save it. Because I can't edit the page I can't change the skin to see if that's what causing the problem. But then again the duplicate that I made from the original does work without any changes to the original settings within the page.

Thank you for the responses....much appreciated.

@molague wrote:

 

-- Reordered & Enumerated for Ease of Reply --

 

Finished upgrading Clearpass 6.6.10 to 6.8 for a customer and after the upgrade users were receiving a "404 Error Page not found" when accessing captive portal guest self-registration page...

 

1. My question is has anyone come across this issue and or is there a way to fix this?

2. We ended up [making] a duplicate of the original self-registration page and configuring the L3 Captive Portal authentication configuration to point to the new self-registration page name.

 

3. The duplicated self-registration page has the original self-registration page as its parent...

4. So we may end up creating a new self-registration page with the settings from the original page, deleting the duplicate and parent pages and renaming the new self-registration page to the original name...

 

---

1. Yes!  We just did the same upgrade and generated the SAME problem! It seems the upgrade process failed to "translate" any of the on-site-created self-registration pages.  Not only did they produce "404" messages when called by a WiFi Client via the controller, attempting to launch them from the ClearPass editing process generated the same results.  The unused, pre-canned page rolled forward just fine.  I am not sure if being pre-canned or being unused was key to having it translate to 6.8 properly...

2. Your actions, as reported here, provided us with the key to unlock a solution!  We simply made the pages without any parent/child relationship!

3. Close to the correct process; again, don't make the Duplicate(s) into Child page(s)! 

4. We made the Duplicate Page as a stand-alone page.  The system appended "_2" to the page name.  We deleted the Original Page, then edited the Duplicate Page and removed the "_2" from the end of the name.  The Captive Portal instantly returned to proper operation!   Total "fix time" (once we settled on the solution) was approximately five (5) minutes -- for "repairing" three (3) broken pages.

I ran into this issue after an upgrade to 6.8.3.110034. I followed the duplicate with parent option set to "Same as original", deleted the original and renamed. I did also notice that I couldn't edit the original (clicking edit returned to the list of pages instantly), but could edit the duplicate. 

ahart has the answer.

I ran into this issue as well upgrading from 6.6.2 to 6.8.4. That was the way to fix it.