search

lcdi / snipe-it

A free open source IT asset/license management system
https://snipeitapp.com
GNU Affero General Public License v3.0
0 stars 0 forks source link

Occassional "D'oh documentRoot" and 404 errors #11

Closed wesbeard closed 3 years ago

wesbeard commented 3 years ago

The hosted installation seems to be working as we've been able to log in and enter items, but occassionally it decides to throw a 404 error while we're working on it as well as one that says "documentRoot should be set to public" which it looks like it is. The errors are not at all consistent and will happen in any browser, but at the same time one browser will work while another won't. I could have firefox and chrome both on the login page where one accesses it just fine but the other gets "D'oh".

image

lenora4321 commented 3 years ago

URL vs rote IP address: image This may be an issue with the /etc/httpd/conf.d/snipeit....... file

lenora4321 commented 3 years ago

Following up to the issue before, I changed the site config files to match "inventory.lcdi" instead of "snipeit.example.com", which made me think to look at the IP address. Why is "inventory.lcdi" associated with 2 IP addresses, .35 and .36? If you go to "inventory.lcdi", I think it might be taking you to 192.168.2.35 instead of where the site is actually at .36. I have yet to encounter an issue with the "D'oh" connecting directly to the IP address, only with the URL. image

lenora4321 commented 3 years ago

Also, did I accidently kill the image on the login screen somehow? Anyone else wanna test on their device? image

lenora4321 commented 3 years ago

Submitted a trouble ticket for this

lenora4321 commented 3 years ago

Trouble ticket got solved, not inventory.lcdi only points to 192.168.2.36, as it should. This did not, however, fix the problem, just narrows down the cause. Next, I'm look at browsers. Every browser I have is able to access the correct site via the URL and IP address, except Chrome, which has trouble only on the URL. See attached screenshot for summary. I want some others to confirm that this issue persists on machines other than mine. image

wesbeard commented 3 years ago

Nice work on this Lenora, Nate and I didn't encounter a "D'oh" at all this shift, trying on multiple browsers, refreshes, etc all on the inventory.lcdi URL. The image thing is an issue and we're looking into it but for the mean time we disabled the images in the branding altogether until we can get it figured out.

lenora4321 commented 3 years ago

So it turns out the issue is pretty much fixed; I just had to flush my DNS cache and that's why I was still getting errors on my end. Command on Windows: ipconfig /flushdns