I installed ZNC as an SPK from the Synology package manager. I believe it is version 1.4. At first everything works great, but after 2 days or so, I can no longer connect to ZNC.
[2015-07-18 10:35:30.851068] (qvazzler/Freenode) IRC -> ZNC [:NickServ!NickServ@ services. NOTICE qvazzler :This nickname is registered. Please choose a differen t nickname, or identify via \x02/msg NickServ identify <password>\x02.]
[2015-07-18 10:35:31.585475] (qvazzler/Freenode) ZNC -> IRC [WHO qvazzler]
[2015-07-18 10:35:36.519269] (qvazzler/Freenode) IRC -> ZNC [:tepper.freenode.ne t 352 qvazzler * ~qvazzler h203n8-g-br-td1.ias.bredband.telia.com tepper.freenod e.net qvazzler H :0 qvazzler]
[2015-07-18 10:35:36.629673] (qvazzler/Freenode) IRC -> ZNC [:tepper.freenode.ne t 315 qvazzler qvazzler :End of /WHO list.]
[2015-07-18 10:35:46.860609] _LISTENER == ConnectionFrom(192.168.1.1, 65231) [Al lowed]
[2015-07-18 10:35:46.860768] There are [0] clients from [192.168.1.1]
What can I do to fix this issue?
Hi all.
I installed ZNC as an SPK from the Synology package manager. I believe it is version 1.4. At first everything works great, but after 2 days or so, I can no longer connect to ZNC.
`mIRC (and other clients) says this:
[10053] Software caused connection abort`
ZNC says this:
```
[2015-07-18 10:35:30.851068] (qvazzler/Freenode) IRC -> ZNC [:NickServ!NickServ@ services. NOTICE qvazzler :This nickname is registered. Please choose a differen t nickname, or identify via \x02/msg NickServ identify <password>\x02.]
[2015-07-18 10:35:31.585475] (qvazzler/Freenode) ZNC -> IRC [WHO qvazzler]
[2015-07-18 10:35:36.519269] (qvazzler/Freenode) IRC -> ZNC [:tepper.freenode.ne t 352 qvazzler * ~qvazzler h203n8-g-br-td1.ias.bredband.telia.com tepper.freenod e.net qvazzler H :0 qvazzler]
[2015-07-18 10:35:36.629673] (qvazzler/Freenode) IRC -> ZNC [:tepper.freenode.ne t 315 qvazzler qvazzler :End of /WHO list.]
[2015-07-18 10:35:46.860609] _LISTENER == ConnectionFrom(192.168.1.1, 65231) [Al lowed]
[2015-07-18 10:35:46.860768] There are [0] clients from [192.168.1.1]
```
What can I do to fix this issue?
<!-- github-sync-id:95815021 -->
The message that you pasted / tried to paste only says that there are 0 other clients from that IP. So, nothing bad.
What's the next thing that znc says?
The message that you pasted / tried to paste only says that there are 0 other clients from that IP. So, nothing bad.
<!-- github-comment-id:122538250 -->
I believe it is version 1.4.
What can I do to fix this issue?
I don't understand the issue, but what you can do is upgrading to supported version (1.6.0).
> I believe it is version 1.4.
> What can I do to fix this issue?
I don't understand the issue, but what you can do is upgrading to supported version (1.6.0).
<!-- github-comment-id:122634755 -->
The issue was caused because I was accessing an external domain pointed to the NAS in the internal network I was in. I fixed it by setting up a DNS server that changes results for my domain, and forwards the rest of the requests to a public DNS. (Source: http://norcats.blogspot.no/2013/01/diskstation-dns-server-sample.html)
The issue was caused because I was accessing an external domain pointed to the NAS in the internal network I was in. I fixed it by setting up a DNS server that changes results for my domain, and forwards the rest of the requests to a public DNS. (Source: http://norcats.blogspot.no/2013/01/diskstation-dns-server-sample.html)
<!-- github-comment-id:122697215 -->
Also, upgrading to 1.6.0 is not possible for me currently on my Synology NAS.
See here: https://github.com/SynoCommunity/spksrc/issues/1457
and here: https://www.bountysource.com/issues/19578768-how-to-update-znc-1-6?utm_campaign=plugin&utm_content=tracker%2F282943&utm_medium=issues&utm_source=github
<!-- github-comment-id:122697273 -->
For the record, the most common cause for [10053] Software caused connection abort is mismatch between SSL and non-SSL on client side and on ZNC listener side.
For the record, the most common cause for `[10053] Software caused connection abort` is mismatch between SSL and non-SSL on client side and on ZNC listener side.
<!-- github-comment-id:122708938 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Hi all.
I installed ZNC as an SPK from the Synology package manager. I believe it is version 1.4. At first everything works great, but after 2 days or so, I can no longer connect to ZNC.
mIRC (and other clients) says this: [10053] Software caused connection abortZNC says this:
What can I do to fix this issue?
What's the next thing that znc says?
The message that you pasted / tried to paste only says that there are 0 other clients from that IP. So, nothing bad.
I don't understand the issue, but what you can do is upgrading to supported version (1.6.0).
The issue was caused because I was accessing an external domain pointed to the NAS in the internal network I was in. I fixed it by setting up a DNS server that changes results for my domain, and forwards the rest of the requests to a public DNS. (Source: http://norcats.blogspot.no/2013/01/diskstation-dns-server-sample.html)
Also, upgrading to 1.6.0 is not possible for me currently on my Synology NAS.
See here: https://github.com/SynoCommunity/spksrc/issues/1457
and here: https://www.bountysource.com/issues/19578768-how-to-update-znc-1-6?utm_campaign=plugin&utm_content=tracker%2F282943&utm_medium=issues&utm_source=github
For the record, the most common cause for
[10053] Software caused connection abortis mismatch between SSL and non-SSL on client side and on ZNC listener side.