metaMMA

Oh cool. I didn't see hexchat on your main images page, so I didn't know you had an IRC client! Correct me if I'm wrong, but I don't think this will quite solve my issue. I'd like to use a BNC on my server to be constantly connected to the IRC channels with playback support. Using hexchat, I could connect to my ZNC over a proxy (privoxy), but that doesn't protect my connection to the IRC networks/channels (would only anonymize the connection to my own server). Ideally I'd like to find a way to have a BNC connect over privoxy, and then use hexchat or another client to connect to the BNC. Perhaps I'm just not understanding the scope of your hexchat container, though. Thanks for the reply. Let me know if there is anything I can do to help.

@binhex I'd like to formally request a `zncvpn` container! I posted a little more information about the subject here

Hi @binhex. First off, thanks for all you do. love your containers, and have been running `binhex-delugevpn` since I moved to unRAID. I'm hoping to get your opinion on something I've been trying to accomplish. I use IRC for quite a bit of communication, and using a BNC (like ZNC) has been very useful. I want to connect to the IRC networks over a VPN, but ZNC does not offer proxy support. To accomplish this, I'm using the `LSIO ZNC` container with a custom network called `container:binhex-privoxyvpn`. I then expose/publish the ZNC port (6501) in the `binhex-privoxyvpn` container, and remove the 6501 port mapping in the ZNC container. This works, as I had hoped. I can hop on any IRC client (as long as I'm on the same network as the unRAID server) and connect to all of my favorite IRC networks/channels (and do so through PIA servers!). The issue is gaining remote access. I'd like to keep ZNC running on my server, but be able to connect remotely. I tested running ZNC in normal bridge mode with 6501 port mapping exposed/published, and I port forwarded 6501 from my server within my router software. Doing this, I could connect to the ZNC container on my server from remote locations (although the traffic was not protected by PIA VPN/privoxy). However, if I then go back to piping the ZNC traffic through the `binhex-privoxyvpn` container, I can no longer connect and checking open ports shows 6501 as closed. I believe I've narrowed down the issue to this statement in the log `Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment`. Can you think of any tips/tricks to getting this to work? Thanks for your time.

Does anyone know of a way to connect to networks over HTTP proxy?

I'm trying to get quassel-core up and running. I can connect via the quassel-web container, but actually saving to the DB is giving me issues. If I attempt to add an 'identity' or 'network', it won't save it to the DB. Clicking 'save' seems to do the same thing as clicking 'cancel'. I'd like to turn debug logging on, if possible. Here's my /config/quasselcore.conf file (it's just the six lines): GNU nano 4.2 quassel-core/quasselcore.conf [Config] Version=1 [Core] AuthSettings=@Variant(\0\0\0\b\0\0\0\x2\0\0\0\x1a\0\x41\0u\0t\0h\0\x65\0n\0t\0i\0\x63\0\x61\..... StorageSettings=@Variant(\0\0\0\b\0\0\0\x2\0\0\0(\0\x43\0o\0n\0n\0\x65\0\x63\0t\0i\0o\0n\0P\.....

1) Hi, I'm preparing to release metaMMA in the next month. Right now, it's in development and I haven't uploaded a version with the "latest" tag. I'll message you once it's ready. 2) I'll have updated instructions in the first post (and on the dockerhub/github sites).

Reserved #3.

Reserved #2.

Reserved #1.

Application Name: metaMMA Docker Hub: https://cloud.docker.com/u/metamma/repository/docker/metamma/metamma Github: https://github.com/metaMMA/metaMMA Please post any questions/issues related to this docker container in this thread. If you are not using Unraid (and you should be!) then please do not post here. Instead head to the 'issues' area on the Github page.

I may have made an elementary mistake, but I can't figure something out. I added a "public automated build" to dockerhub: https://hub.docker.com/r/metamma/sonarr-trakt-tv/ And it shows up just fine when searching CA with dockerhub enabled. Myself and other can download/install it just fine. But it is showing up as a "private repo" in the CA search. Can anyone help me get this changed to public?