-
Notifications
You must be signed in to change notification settings - Fork 19
IOS unable to reach server #18
Comments
Also seeing this on previously working app setups. I've tried removing the app and settings and logging in again, still fails. |
Thanks for the notice, I'll look into this right away |
@tlkhorses @twelch24 Okay, this seems to be an issue with servers and cors not enabled. My apologies, on the new iOS update in ionic it enforces this and I have it enabled so I didn't notice this issue. https://github.com/librenms/librenms/blob/master/doc/Support/Configuration.md#cors-support |
Hi, I added the cors enabled to the config.php and didn't work. Added the whole section, restart and still no go. |
It does fix it for me. Did you copy and paste the false line?
All I added was the first line, and changed it to true.
… On Jan 12, 2018, at 5:36 PM, tlkhorses ***@***.***> wrote:
Hi, I added the cors enabled to the config.php and didn't work. Added the whole section, restart and still no go.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Thats the first thing I did. No go. Then added the whole section. Same. I'm
checking with my tech to make sure he can reach the server via browser from
where he is at.
…On Fri, Jan 12, 2018 at 5:52 PM twelch24 ***@***.***> wrote:
It does fix it for me. Did you copy and paste the false line?
All I added was the first line, and changed it to true.
> On Jan 12, 2018, at 5:36 PM, tlkhorses ***@***.***> wrote:
>
> Hi, I added the cors enabled to the config.php and didn't work. Added
the whole section, restart and still no go.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJBxbTapjgn1R_AiMRJrrx85g0EzlAP3ks5tJ_A3gaJpZM4Rc3TF>
.
|
He can reach it via browser on the phone. I checked global on the server and it shows enabled. |
Check the web server logs. On one install of mine without cors I see:
Also, get them to try a manual curl if they can using the token to see if it works:
|
1.2.1 push to apple store. Pending approval, with cors fix. |
@laf where are the server logs? Only see /var/log/... stuff. |
1.2.1 is available on iOS so you should be able to remove the cors config if you wish @tlkhorses the server logs will be in your librenms directory I believe Default "/opt/librenms/logs/access_log" |
The update fixed the issue for us. Thanks. |
We have an issue where iPhones get the message Unable to reach server. Software was just downloaded yesterday so is current. Android is working via app. The iPhones meet the requirements and are set up with tokens and proper url. They both can log in via browser. This happens both via wifi, cell on and off network.
The text was updated successfully, but these errors were encountered: