binhex

Community Developer
  • Posts

    7879
  • Joined

  • Last visited

  • Days Won

    37

Everything posted by binhex

  1. I see, so you do need a working incoming port, that is going to be tricky, as i mentioned the port is dynamic for pia (other vpn providers permit static incoming port), so even if you find out what the port is you would then need a programmatic way of configuring soulseek to use it, otherwise you would need to manually reconfigure soulseek each time the port changes. so is it possible?, yes but its going to require some work on your part to configure soulseek.
  2. looks related:- https://www.planetminecraft.com/forums/help/bedrockedition/bedrock-server-smithing-table-error-after-1-20-update-673307/ btw i too see this but i had forgotten about it 🙂
  3. The PIA incoming port is dynamic so every time you restart the container or the vpn drops and re-establishes you may have a new port number, what is it you are trying to achieve?, access a web ui of a container externally?
  4. A quote from the reply:- Already done, it is bound to the vpn interface, and we also specify the vpn adapters ip for incoming, so yeah not much else i can do here unless im missing a setting in the ui. from my previous post:- i see you included this in your post, ok he does go on about setting the incoming adapter but there is no way to do that, you can only set the incoming address, and if you try and force this by editing the core.conf it simply errors, so i dont know how to achieve this, it must be some hackery of libtorrent probably via itconfig i assume.
  5. If this is repeatable (which by the sound of the above it is), then restart the container, wait for the issue to occur and then docker exec inside the container and issue the following command which will reveal your external ip, it should be your vpn provider assigned ip:- curl http://ifconfig.co if it is your vpn provider ip then raise a bug with deluge, detail that you have the vpn provider adapter bound in deluge for 'outgoing interface' and the ip address of the vpn adapter defined for 'incoming address' yet the external ip address shown is your isp ip address and see what they say.
  6. This must be a bug with how deluge detects your external ip address, it is clearly bound to the vpn adapter (as shown in your last screenshot - wg0) and it is advertising your vpn ip, as shown by whatismyip.net, on top of this there are strict ip table rules in place to prevent ip laakage, so there is no way for deluge to connect to peers via your isp connection. FYI i cannot replicate the bug on my system, are you running the latest image?.
  7. can you also post a screenshot of deluge web ui preferences/network
  8. where do you see this?, in deluge web ui?
  9. see here for the keys above:- https://github.com/binhex/documentation/blob/master/docker/guides/vpn.md No, the port you are seeing is a temporary incoming port assigned to that particular session, the other thing to note is that VPN_INPUT_PORT is NOT to be configured as an incoming ports for torrent clients, this can lead to ip leakages, see note in link above. I think what you are trying to achieve is covered in Q24:-https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
  10. do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md
  11. No cloudflare at all, i simply use a port forward for the few apps that need exposing for people outside of my family, as in Plex and Minecraft and then everything else is accessible via wireguard running on my pfsense router. I think as long as you have regular backups of your world and force microsoft authentication then the risks are low, i have never had a griefer or hacker attack my server to date, you could employ 'wihte-list' of players so that only set accounts can connect for added security.
  12. im assuming you are talking about urbackup here not unraid, in that case you would:- 1. stop the urbackup container 2. delete all backup data stored on unraid 3. delete all files and folders located in the /config folder for this container 4. start container and reconfigure
  13. Nope, i run this myself, no disconnection issues, maybe network related, try a hard wired minecraft client to rule out wi-fi being the issue.
  14. OK so you have had your server hacked and are being held ransom (ransomware) for decryption, this is a bigger issue!, please firstly identify the cause of the server being hacked and fix it, then consider your next move.
  15. This is a terrible idea, i'm just highlighting this for the next person, please do NOT do this, there is a Web UI for urbackup for a reason, please delete images and backups using the UI, otherwise urbackup will be unaware of your manual deletion. This is the wrong path, the urbackup databases are located at /config/urbackup/ TBH i would recommend you try asking for help on the urbackup forum, they should be able to guide you on the best way to fix this.
  16. you can see the versions as tags for the images, you can see the ful list of images here:- https://hub.docker.com/repository/docker/binhex/arch-minecraftbedrockserver/tags?page=1&ordering=last_updated if you want to use a specific version then append :<tag version> to the repository for the container.
  17. Ha yes you are quite right, it does appear that qbittorrent process has not started, the config of the port was fooling me here, OK so most probably a config related issue, you could try restoring your config from a backup from when it was working, or simply let qbittorrent re-create the default, if you want to do this then simply rename the file /config/qbittorrent/config/qBittorrent.conf and then restart the container to re-generate the file, you will then need to reconfigure again of course but i expect it will get you access again.
  18. that SHOULD get you access to the web ui as long as you didn't change the value for env var 'WEBUI_PORT', this is set to 8080, correct?.
  19. nope, nothing wrong with port forwarding according to your latest attached log, that is working as expected. Incoming port is not defined at the container level, it is defined by your VPN provider, port 6881 is included as a incoming port if you do NOT use the VPN part of the image, i.e. VPN_ENABLED = no, which is not the case for you. What is the IP address of the machine running the web browser that you are using to attempt connection to the web ui? is it 192.168.178.xxx ?
  20. Do this:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md
  21. looks like permissions related issue, from your snippet above:- cannot touch '/tmp/dnsfailure': Permission denied from your supervisord log i think you have dns set to an internal name server which results in name lookup failure:- nameserver 10.128.0.1 set NAME_SERVERS to the default values:- NAME_SERVERS=84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1
  22. See this is why I know I will never work for LT I simply don't own one of these shirts [emoji16]...... Unless you give them out for free when joining? Sent from my 22021211RG using Tapatalk
  23. Nice clear instructions on setting up i2p for qbit https://strict3443.codeberg.page/i2p-info/hugo/public/posts/how-to-use-i2p-on-qbittorrent-nox/ Disclaimer: not tested it yetl Sent from my 22021211RG using Tapatalk
  24. My wish list (voted other), in no particular order:- Native Docker Compose support and incorporate new functionality into the Web UI. Create mobile friendly Web UI. Create official API so that third party apps can link and control unRAID (Android/IOS app).
  25. Im also on Gigabit and I run this docker image myself, latest backup stats for me reveal:- Writing new file list... All metadata was present Transferred 760.776 MB - Average speed: 36.7041 MBit/s So yeah, not lightning fast, but that is probably more to do with the speed of the Windows filesystem and the fact it has to scan and backup lots of little files (not something Windows is particularly good at), i would suspect if i was backing up large files my speeds would be significantly higher.