This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About Sean_Small
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- LIVEcommunity
- About Sean_Small
Online
1Post
1Like
1Solution
Jul 06, 2022Last Visited
User
Activity
User
Profile
Latest posts by Sean_Small
| Subject | Views | Posted |
|---|---|---|
| 774 | 03-25-2022 08:04 AM |
My Liked Posts
| Subject | Likes | Posted |
|---|---|---|
| 1 Like | 03-25-2022 08:04 AM |
Posts I Liked
| Subject | Likes | Author | Latest Post |
|---|---|---|---|
| 1 Like |
User Badges
Community Statistics
| Member Since | 04-30-2021 07:21 AM |
| Date Last Visited | 07-06-2022 10:27 AM |
| Posts | 1 |
| Total Likes Received | 1 |
03-25-2022
08:04 AM
1 Kudo
The accepted solution "TLS_REQCERT never" is not really a fix. This only bypasses cert checking. If you are running into this issue it's because your company run's their own root CA and you generated a cert for expedition from it. So you need to put your local cert into the Linux cert store.
Proper fix:
$ sudo cp local-ca.crt /usr/local/share/ca-certificates
$ sudo update-ca-certificates
... View more
LEGAL NOTICES
Copyright 2007 - 2022 - Palo Alto Networks