Error deleting custom URL categories?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Error deleting custom URL categories?

L4 Transporter

I created a custom URL category and then tried to delete it and got this on the validate, any ideas please?

Operation           Validate

Status   Failed

Details  member corp-blocking-exclusions is an invalid reference

Invalid block

Invalid url-filtering corp default

Invalid url-filtering

Invalid profiles

Invalid vsys vsys1

Invalid vsys

Invalid configuration for localhost.localdomain

Invalid devices

Any ideas please?

This is on 3.1.1, doesn't appear to matter if the category is set to block/allow or anything else in the URL profiles.

Thanks in advance.

13 REPLIES 13

L5 Sessionator

This is a bug that was fixed in 3.1.2.

OK I've just upgraded to 3.1.2 and still can't delete these custom categories, when I try to I get:

Delete failed for the following:

corp-blocking-exclusions: The specified object(s) cannot be deleted because of references in one of the following object(s):

custom-url-category url-filtering corp default

I've tried with the url filtering profile set to allow and block for that custom url category and it makes no difference - what am I missing please?

Thanks.

You have to delete any filters using the custom category before you can delete the category.  Similarly, if you have a policy using a filter in which there is a custom category, you have to delete the policy as well.

OK sorry can you explain that a bit more step by step please?

I created some URL categories and put some URLs in them.

They automatically show up in all my URL Filtering Profiles, I've not specifically added them.

What exactly do I need to do to delete the custom categories please?

The error message you received indicates that URLs assigned to your custom category were used in block or allow lists in a URL filter called " corp default" .  If you delete the "corp default" URL filter, (won't work to just delete the URLs in the "corp default" filter), you should be able to delete your custom category.

So you're saying if I have a URL filtering profile "Corp Default" that had www.domain.com in its allow list section, and I then remove www.domain.com from the allow list and add it to a custom URL category, I can't delete that custom URL category without deleting the entire original "Corp Default" URL profile, which is used on all manner of access rules...?

Have I misunderstood, because if that's correct surely that can't be by design as it just seems plain broken?

I presume I could clone "Corp Default" to at least save a little of the duplication work needed here?

Engineering is looking into allowing the deletion of categories irrespective of references and then automatically cleaning up the references.  In the meantime, you need to delete either the policy or profile in which the URLs listed in the custom category are used.

Hi,

Is there any update on if/when this feature will be available please?

Thanks.

Looks like end of this month time frame.

Cool thanks.  Sounds like maybe in 3.1.4 then (I'm assuming 3.1.3 is finalised and awaiting release).

L4 Transporter

Are we any nearer to being able to do this please?

Engineering is targeting 3.1.4 due out mid-August, though it is not finalized that it will be in that release.

I have a Palo Alto in 3.1.4 and this error still persist.

  • 4267 Views
  • 13 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!