-
Notifications
You must be signed in to change notification settings - Fork 95
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dsmr webinterface reports blank... (iOS + port 10080) #1436
Comments
Thanks, but also there it shows only the blank part without any gets. Seems like the gets are being dropped when sent by any ios browser but not through mac browser. Funny thing is that the curl requests do come through from both devices. So no firewall issues or anything. Although i did notice some code within dsmr script about standalone (only applicable to safari)? But still weird that I would be the only one experiencing this…
… On 15 Aug 2021, at 12:54, Dennis Siemensma ***@***.***> wrote:
You may want to start with pressing F12 or whatever brings up the developer tools in de browser. Then check the Console tab for any errors and the Network tab to see what status code the requests return. Either may give more information about why it fails.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
Unfortunately I do not have an iOS device to test with, so you'll need to be really specific. From a technical point of view, I see no obvious reason for requests to be handled differently.
If requests were sent but dropped by the server, you should see failing requests. If no requests are sent at all, in two browsers on the same device, it's gonna be really hard to debug those. To be clear, you did try the developer tools on the iOS device? https://developer.apple.com/safari/tools/
Could you point to the code so I can check out if it's related or not?
Is this the webserver serving DSMR-reader or is it another proxy in front of it? If you can't find any other clues, you may want to debug the Nginx server to see whether it receives any request at all from the browsers, and therefor whether the browsers are causing the issue or something else. |
Ok, I have found the culprit. Apparently port 10080 (the one that I was using as an alternative to port 80) has been silently closed on iOS Safari or so it seems (following Chrome and Firefox I suppose). Although I can’t find any reference from apple on the matter (although I am running an iOS beta, but strangely enough my other iPhone runs non-beta iOS and that one as well blocks port 10080. So changing the port solved the problem for me!
Thanks for helping out @dennis Siemensma
… On 15 Aug 2021, at 21:46, Dennis Siemensma ***@***.***> wrote:
Assigned #1436 <#1436> to @JeeKee80 <https://github.com/JeeKee80>.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <#1436 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQFSEN5QXXFG5FS27WB2G6TT5AKSFANCNFSM5CGBARFA>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>.
|
Great and thanks for sharing the info as well! |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hi guys,
I am kinda lost, but my dsmr webinterface gives me blank when accessing it with iOS safari\chrome or directly from my pi. If I access the webinterface with my mac it show as it should. I am using NGINX as server running on a pi to only offer local access. dsmr is up-to-date, python 3.7 and pip 21.2.
DSMR webinterface is running as it should. If I use curl I always see a GET request. No errors\warnings in the NGINX logs.
Any ideas?
The text was updated successfully, but these errors were encountered: