Skip to content

Commit af9eef0

Browse files
authored
HTTP error 403
1 parent dc88748 commit af9eef0

File tree

1 file changed

+26
-2
lines changed

1 file changed

+26
-2
lines changed

README.md

Lines changed: 26 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# Linux-Troubleshooting-Scenarios-with-solutions
2-
Linux Troubleshooting Scenarios based question with solutions
2+
Linux Troubleshooting Scenarios based question with solution approach
33

44
Its crucial to understand the problem statement before proceeding for any action. The first action should not be to rush out to server side and try to troubleshoot the issue. The first approach would be is to try to understand the issue and ask the user/client follow up questions to understand the problem properly. Its often happen that the issues are on the client/user side who reported it and lot of the time get spend into understand or even become impossible to get it resolved. So don't preassume that your client/user would be technical and whatever the shared information is 100% right. We have to ask the questions to build the facts for the formation of right direction.
55

@@ -333,7 +333,31 @@ These above reasons and resolution can be mapped on other issues like can't exec
333333

334334
</details>
335335

336-
336+
337+
<details>
338+
<summary>HTTP error 403: forbidden yum occurs when we try to install a package using yum</summary>
339+
<i>The HTTP 403 Forbidden response status code indicates that the server understands the request but refuses to authorize it. The access is permanently forbidden and tied to the application logic, such as insufficient rights to a resource. [Ref](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403 , https://bobcares.com/blog/http-error-403-forbidden-yum/)</i>
340+
<!--All you need is a blank line-->
341+
342+
.
343+
├── There could be some major causes during installing pkg from yum
344+
│ ├── Network configuration
345+
│ │ ├── If you are using proxy server
346+
│ │ │ ├── check the proxy setting in the /etc/yum.conf as its effective rather than using env variable #export https_proxy=https://<ip/hostname>:<port>
347+
│ │ │ │ ├── If the proxy server is valid
348+
│ │ │ │ │ ├── Check the ACL on the proxy server
349+
│ │ ├── Other
350+
│ ├── A corrupt repo
351+
│ ├── Permission of packages
352+
│ │ ├── This option most ofently not used because we linux manages by itself so avoid to proceed for this option. The use of this option irresponsibly could make the system unstable
353+
│ ├── Selinux issue
354+
│ ├── firewalld rules
355+
│ ├── Other
356+
└── ...
357+
358+
</details>
359+
360+
337361
<details>
338362
<summary>Some Linux Helpful Commands</summary>
339363
<!--All you need is a blank line-->

0 commit comments

Comments
 (0)