2020-05-27, 20:13
@mufflon12
I would hold off on the log until the next alpha if possible. The current log could still be useful though.
I am working on another alpha continuing the implementation of the custom access urls. There are lots of changes are the url handling and processing so it may indirectly resolve your issue.
Before posting a log in the thread I would sanitize it a bit first. Find and replace any server ips with .'s or -'s, and any *Token=<token>. The add-on hides this as best as possible but some leaks through with Kodi's logging. You're also welcome to email it as well. same username [at] gmail.
@komplex
It's up to you, if you want to open an issue on GitHub. Whichever is easier for you is fine with me.
That said, I have nginx up and using the same configuration as you now. A couple things left to iron out, but I think those will be pretty straight forward.
I'm hoping to have a new alpha up tonight or tomorrow
I would hold off on the log until the next alpha if possible. The current log could still be useful though.
I am working on another alpha continuing the implementation of the custom access urls. There are lots of changes are the url handling and processing so it may indirectly resolve your issue.
Before posting a log in the thread I would sanitize it a bit first. Find and replace any server ips with .'s or -'s, and any *Token=<token>. The add-on hides this as best as possible but some leaks through with Kodi's logging. You're also welcome to email it as well. same username [at] gmail.
@komplex
It's up to you, if you want to open an issue on GitHub. Whichever is easier for you is fine with me.
That said, I have nginx up and using the same configuration as you now. A couple things left to iron out, but I think those will be pretty straight forward.
I'm hoping to have a new alpha up tonight or tomorrow
