-
Notifications
You must be signed in to change notification settings - Fork 53
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
Parsing error #186
Comments
I'd guess your calendar URL started responding with the wrong content - can you try your calendar URL in a browser or curl/wget, and take a look if it's a valid iCalendar feed? |
No, URL is working perfectly (tested with Browser and Thunderbird). I'm querying Nextcloud all the time. It was working as before, but after the git pull this morning it stopped.
|
I just deleted the module and did a new git clone etc.. Error remains. |
Can you still tell from which commit sha you came and which one you tested? Maybe try commenting in https://github.com/MMM-CalendarExt2/MMM-CalendarExt2/blob/main/node_helper.js#L91 and take a look if the XML document you get has maybe a text section describing what went wrong. |
Hi - sorry for the longer delay.
The log ist than still showing the same errors:
Info:
On a RaspPI |
Could you please try the things I suggested in my last comment? |
|
Hm, than it definitely was not a81cf67. What does activating the |
Found it. My pwd is outdated :-/ It was not visible and while testing in browser it was ok. Strange. So problem solved and sorry for the "stress". Maybe a hint in the log about some issues while fetching the data from the server would help troubleshooting? |
That's a good one - I get how the browser testing was okay, since you probably used that very browser to change the password. The "hint in the log" is exactly that - if the server does not clearly tell that there is an authorization problem - which I guess it didn't since it instead responded with an XML page - the parsing error is the only thing left. If there would have been a proper 403 error it should have been caught in https://github.com/MMM-CalendarExt2/MMM-CalendarExt2/blob/main/node_helper.js#L98-L103 Could you please try the request with |
I forgot to post the MMM-log output:
which is than also what you see in curl:
|
Your curl output cuts of the HTTP status header, which would be the biggest clue. Could you copy the rest in? |
it's 401:
|
Okay, that's definitely something we should be able to catch |
Today I updated the local repo with your commits and startet again MM. The system was running before without any issues.
Unfortunatelly the calendar doesn't come up:
[CALEXT2] calendar:VWXYZ>> invalid line (no token ";" or ":") "<?xml version="1.0" encoding="utf-8"?>
Was there an update on a parser? Do I need to update somewhere the current config to make it running again?
The text was updated successfully, but these errors were encountered: