Welcome to OCS Inventory NG community support, where you can ask questions and receive answers from other members of the community.

Please ask questions only in English or French.

Release 2.12.3 available

The official documentation can be found on https://wiki.ocsinventory-ng.org. Read it before asking your question.

Troubleshooting 403 errors in agent checkin

New install of ocsinventory, all modules on the same (debian) server.  /ocs-reports seems to be working fine now, but when I install the agent on a test machine it can't reach the server module located at /ocsinventory

The relevant line in the agent logs is:

ERROR *** AGENT => Failed to send Prolog <HTTP Status Code #403>

I've also tried manually pointing a browser at http://x.x.x.x/ocsinventory and I do indeed get a 403 error.  When I do the same from the server itself I get a blank page, which I assume is intended.

I do not have a firewall or any network-level blocks between the agent computer and the server.  I assume I have misconfigured something.

If I compare permissions between /usr/share/ocsinventory-reports and /usr/share/ocsinventory-server, the only difference is that /ocsinventory-reports is owned by www-data www-data and ocsinventory-server is owned by root root.  Is it possible that's the source of my problem? I'm hesitant to just go changing owners without fully understanding who the owner is *supposed* to be.
in OCS Inventory NG server for Unix by (290 points)

2 Answers

0 votes

Went ahead and changed those permissions, to no avail.

Confirmed that ocsinventory-server.conf and z_ocsinventory-server.conf are the only files that touch the <location> /ocsinventory and they still have the default config:

---snip---

  1. <Location /ocsinventory>
  2. <IfModule mod_authz_core.c>
  3. # Apache 2.4
  4. Require all granted
  5. </IfModule>
  6. <IfModule !mod_authz_core.c>
  7. # Apache 2.2
  8. order deny,allow
  9. allow from all
  10. </IfModule>
---snip---
ago by (290 points)
0 votes
Where is yours checks of Apache configuration and Apache access log files ? Without these checks, there is no chance to solve ...

Please check : apache2ctl -S and access.log
ago by (20.8k points)
 
Powered by Question2Answer
...