search

diegogarciadev / android_snipeitapp_config

Automatic configuration of Android SnipeIT APP
27 stars 13 forks source link

File /snipeitapp_config.php not found in server #44

Open Alex9001 opened 4 months ago

Alex9001 commented 4 months ago

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

  1. open cpanel softaculous installer
  2. Install snipeit-app
  3. Log in and create API key
  4. Upload snipeitapp_config.php to / and enter API key
  5. Verify that https://snipeit.server.com/snipeitapp_config.php is accessible by browsers
  6. snipeit android application claims File /snipeitapp_config.php not found in server (NOT TRUE)

Expected behavior Connect to the server and work normally

Screenshots

Screenshot_20240422-041432

Desktop (please complete the following information):

Smartphone (please complete the following information):

Additional context Add any other context about the problem here.

diegogarciadev commented 1 month ago

Weird, we tried to access the url you put in the field plus the file name, so there is no other check before trying the connection...

Bellwether commented 1 month ago

I'm having the same issue. cPanel, SnipeIT Version v5.0.10 - build 5680 (master). Android App version 0.7.6. Let me know how I can 1) help provide additional information, and 2) how I can help (financially or otherwise) provide resources to address this issue. :-)

chip0lino commented 1 month ago

I have the same issue. please help!!!

jbliss0 commented 4 weeks ago

I'm having the same issue, except it is an on premise installation of Snipe-IT.

jbliss0 commented 4 weeks ago

I'm having the same issue, except it is an on premise installation of Snipe-IT.

I figured out my issue... In the server address I had to put the full path, including the public folder. Working now!

diegogarciadev commented 4 weeks ago

I'm having the same issue, except it is an on premise installation of Snipe-IT.

I figured out my issue... In the server address I had to put the full path, including the public folder. Working now!

Can you send me an screenshot? I don't know why you have to put the public dorectory if it works without it in the browser...

jbliss0 commented 4 weeks ago

I'm having the same issue, except it is an on premise installation of Snipe-IT.

I figured out my issue... In the server address I had to put the full path, including the public folder. Working now!

Can you send me an screenshot? I don't know why you have to put the public dorectory if it works without it in the browser...

It's only on my PC that I don't have to use the full path. I forgot to mention that part in my initial comment. I have to put the full path in my mobile browser too. In fact, that was how I realized I needed to use the full path. I was using my phones browser to see if it was a pathing issue.

The reality for my situation is that I probably have a DNS issue that caused this problem for me. I say this because I have to use the server's IP address and not the name. I'll figure that part out later though... lol.

Thanks for reaching out and trying to help!

Josh

diegogarciadev commented 4 weeks ago

I'm having the same issue, except it is an on premise installation of Snipe-IT.

I figured out my issue... In the server address I had to put the full path, including the public folder. Working now!

Can you send me an screenshot? I don't know why you have to put the public dorectory if it works without it in the browser...

It's only on my PC that I don't have to use the full path. I forgot to mention that part in my initial comment. I have to put the full path in my mobile browser too. In fact, that was how I realized I needed to use the full path. I was using my phones browser to see if it was a pathing issue.

The reality for my situation is that I probably have a DNS issue that caused this problem for me. I say this because I have to use the server's IP address and not the name. I'll figure that part out later though... lol.

Thanks for reaching out and trying to help!

Josh

And if you have to put "public" in the url is because you have an apache misconfiguration, the documentroot needs to be public folder