[Support] binhex - DelugeVPN


Recommended Posts

Bnihex-deluge shows freespace decreasing

I was told to post in this thread for some advice, when I look at the available space on my array from the main tab of unraid it says that the array has 82.0TB available, when I open the deluge webUI it currently says 77344.1GB but is decreasing by 0.1-0.2 every second. All of my torrents were completed downloading and seeding and I have since paused everything as well but the freespace is still decreasing. This seems like a deluge error since the main tab of unraid shows that the freespace is not changing. Any ideas what could be causing this and how I can fix it so that I actually have the freespace I'm supposed to? If someone could walk me through exporting logs from deluge that would be great as well as I don't see an option in the WebUI to do that.

TIA 

Link to comment
On 6/18/2022 at 4:11 PM, Scriphy said:

deluge webUI it currently says 77344.1GB but is decreasing by 0.1-0.2 every second.

what deluge thinks is free space will depend on what you are pointing incomplete and completed folders to, for instance for me free space is 500GB, even though my array is much larger, this is because incomplete and completed are set to point at my cache disk and as you would expect, deluge is not aware of unraid or arrays so can only see free space on my cache drive. 

 

so going back to your issue, see where incomplete and completed are saving to, is it to the array for both or are you downloading to your cache drive (assuming you have one).

Link to comment

[DelugeVPN PIA and PortForwarding]

 

Anyone else recently getting this issue (which has popped up quite a bit before)

 

"Unable to successfully download PIA json to generate token from URL  'https://www.privateinternetaccess.com/gtoken/generateToken'"

 

I am using the connection (which supports port fowarding):  remote swiss.privacy.network 1198

 

Is this an issue with PIA not supporting Port Forwarding on OpenVPN?  Is it an issue with PIA running out of ports to hand out?  The problem goes away when I set "STRICT_PORT_FORWARD=yes"

 

Thanks in advance for the help.  I LOVE DelugeVPN, thanks for all who have contributed !

 

 

 

Link to comment
Posted (edited)

i am so sorry to ask this question "again"

 

I recently needed to re-initialise my nas, just after when i finally got things working again docker wise. This because there were issues with the initial nas initialisation, which seemed to have  nothing to docker related). 

Unfortunately I haven't been able to connect to the webUI (which has seem to have started) of DelugeVPN since then.

 

I verified my  LAN network ip in the stack as this was the silly error i over looked last time i asked a question related to a topic, with similar issues.

( LAN_NETWORK=192.168.178.1/24), while my NAS is running on IP:192.168.178.45

 

I used the ports as standard (basically using the same stack as always) so i try to connect via.

192.168.178.45:8112, but it time's out.

 

So as i read through a similar (very similar indeed) issue here in this thread i verified the following.

1:) VPN subscription is paid for and working, which it is.

2) VPN end point is not down, which it isn't as i used the same end point on my laptop without issues.

Never the less if I turn VPN off (VPN_ENABLED=no) there is no issue to connect to the WEBUI at all, but ofcourse then i loose the protection on the VPN.

 

Additionally i checked that there were no issue with my login credentials (actually recreated a new password) but unfortunately, to no avail.

 

Honoustly, now i have absolutely no idea what to look for, any thoughts / sugestions?

 

As looking at the logs, all is supposed to be running fine, in the console all also seems to be fine.

 

stack:

version: "2.1"
services:
  arch-delugevpn:
    image: binhex/arch-delugevpn:latest
    container_name: DelugeVPN
    cap_add:
      - NET_ADMIN
    environment:
      - VPN_ENABLED=yes
      - VPN_USER=LPRyc2GmAjUbxtuGThtm....
      - VPN_PASS=KZ2qpsTxCTfCBBTgfxxj....
      - VPN_PROV=custom
      - VPN_CLIENT=openvpn
      - STRICT_PORT_FORWARD=yes
      - ENABLE_PRIVOXY=yes
      - LAN_NETWORK=192.168.178.1/24
      - NAME_SERVERS=209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1
      - DELUGE_DAEMON_LOG_LEVEL=info
      - DELUGE_WEB_LOG_LEVEL=info
      - ADDITIONAL_PORTS=1234
      - DEBUG=false
      - PUID=111
      - PGID=321
      - UMASK=022
    volumes:
      - /volume1/Docker/DelugeVPN/Config:/config
      - /volume3/Movies/Downloads:/download
      - /etc/localtime:/etc/localtime:ro
    ports:
      - 8112:8112
      - 8118:8118
      - 58846:58846
      - 58946:58946
    restart: always

 

 

_DelugeVPN_logs.txt

Edited by spikey1973
Link to comment
8 minutes ago, spikey1973 said:

I verified my  LAN network ip in the stack as this was the silly error i over looked last time i asked a question related to a topic, with similar issues.

( LAN_NETWORK=192.168.178.1/24), while my NAS is running on IP:192.168.178.45

You got it wrong this time too, it should be 192.168.178.0 :)

  • Like 1
Link to comment

@ Members:

 

thnk you so much again. indeed this did it again. guess i am still not onboard with ip's as i thought i was.

Never the less, what i wonder is why could i connect with VPN off, with the same IP settings?, to me that would mean i shouldn't have been able to connect either, but as i said... i could.

 

Kindest regards and appreciation!

 

Link to comment
4 minutes ago, spikey1973 said:

Never the less, what i wonder is why could i connect with VPN off, with the same IP settings?

With VPN off there are no iptables rules in place, but with VPN enabled there are very strict iptables rules in place to prevent leaking.  

  • Like 1
Link to comment

 

I know that this likely isn't a problem with delugevpn specifically but I haven't been able to find any answers anywhere that solve my issue. I was using delugevpn for about a week and it was working perfectly as expected then out of the blue everything slowed to a halt and stopped working. I saw there were issues with privoxy running and i turned it off and switched to binhex privoxy but after a couple hours delugevpn slowed again and came to a stop. i've tried reinstalling, i've tried binhex/deluge and it hasn't improved. I tested a torrent on binhex/qbittorrent as well but had no issues. on my most recent reinstallation of delugevpn it worked on 2 torrents and was partially through another. Now it occasionally is able to seed the completed torrents but it's not downloading new torrents and no longer seeding.

I tested removing possible faulty trackers but no luck. Currently my torrents say tracker status Announce OK but nothing is coming through. There do appear to be peers that should be able to allow the download process but i believe its an issue i'm having locally. I know this is likely not an issue with delugevpn but likely my setup but couldn't find another place to ask for help. Any help would be greatly appreciated. I can also supply any needed information that is needed. Currently i'm also not finding many useful details on these errors on my logs (dozzle)

Link to comment
2022-07-04 02:17:49,844 DEBG 'watchdog-script' stderr output:
Unhandled error in Deferred:

2022-07-04 02:17:49,844 DEBG 'watchdog-script' stderr output:

Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 858, in _runCallbacks
    current.result = callback(  # type: ignore[misc]
  File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 1338, in _cbDeferred
    self.callback(cast(_DeferredListResultListT, self.resultList))
  File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 662, in callback
    self._startRunCallbacks(result)
  File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 764, in _startRunCallbacks
    self._runCallbacks()
--- <exception caught here> ---
  File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 858, in _runCallbacks
    current.result = callback(  # type: ignore[misc]
  File "/usr/lib/python3.10/site-packages/deluge/ui/web/json_api.py", line 187, in _on_rpc_request_failed
    return self._send_response(request, response)
  File "/usr/lib/python3.10/site-packages/deluge/ui/web/json_api.py", line 229, in _send_response
    response = json.dumps(response)
  File "/usr/lib/python3.10/json/__init__.py", line 231, in dumps
    return _default_encoder.encode(obj)
  File "/usr/lib/python3.10/json/encoder.py", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/usr/lib/python3.10/json/encoder.py", line 257, in iterencode
    return _iterencode(o, 0)
  File "/usr/lib/python3.10/json/encoder.py", line 179, in default
    raise TypeError(f'Object of type {o.__class__.__name__} '
builtins.TypeError: Object of type Failure is not JSON serializable

Unhandled error in Deferred:

Traceback (most recent call last):
Failure: deluge.error.NotAuthorizedError: Auth level too low: 0 < 5


2022-07-04 02:18:01,993 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2022-07-04 02:18:02,088 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com'

I get this error when I try to add a torrent to Deluge. I'm not sure what it means but I can't add torrents via magnet URL or .torrent files.

Thank you!

 

Link to comment
Posted (edited)

Hi, hopefully someone can assist me. I've got binhex containers on my system (DelugeVPN, Sonarr, Radarr, Prowlerr), but something has happened recently and I can no longer access the WebUI for Radarr, Sonarr and Prowler via their IPs. I have not made any changes to the system, though there have been updates. I originally set them up to run through delugeVPN, so I'm thinking this may have something to do with it, as it is only the Sonarr, Radarr and Prowlerr containers that are having issues. Could anyone advise as to what may have happened, and how I can avoid whatever has happened from happening again?

 

I notice my containers don't have a Host Port in their settings, but when I try to add it, I get an error (see below for Radarr example). Once that happens, the docker image becomes orphaned and I have to reinstall it and remove the Host Port so the container will actually install.

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-radarr' --net='container:binhex-delugevpn' -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="UnraidServer" -e HOST_CONTAINERNAME="binhex-radarr" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[ip]:[port:7878]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/radarr-icon.png' -p ':7878/tcp' -v '/mnt/user/Downloads/':'/data':'rw' -v '/mnt/user/Media/Films/':'/media':'rw' -v '/mnt/user/appdata/binhex-radarr':'/config':'rw' 'binhex/arch-radarr'
docker: Error response from daemon: conflicting options: port publishing and the container type network mode.
See 'docker run --help'.

Edited by takkischitt
Link to comment

I'm having a issue with Deluge VPN.  Right now all my torrents are not updating their trackers and are sitting at no seeders or peers.  I use PIA and have tried connecting to different ovpn servers and haven't had any luck.  Here's the current log for the docker.

 

2022-07-05 13:21:26,373 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'tun0'
[info] Deluge key 'outgoing_interface' will have a new value 'tun0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-07-05 13:21:26,854 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of '51cb5aaae02ac52ca9d32c0434a98e12d4fac639'
[info] Deluge key 'default_daemon' will have a new value '51cb5aaae02ac52ca9d32c0434a98e12d4fac639'
[info] Writing changes to Deluge config file '/config/web.conf'...

2022-07-05 13:21:27,589 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2022-07-05 13:21:27,923 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2022-07-05 13:21:32,721 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2022-07-05 13:21:32,721 DEBG 'watchdog-script' stderr output:
<Deferred at 0x146235b76d10 current result: None>

2022-07-05 13:21:37,825 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (44187, 44187)
Configuration value successfully updated.

2022-07-05 13:21:37,825 DEBG 'watchdog-script' stderr output:
<Deferred at 0x14ffe7286b60 current result: None>

2022-07-05 13:21:42,935 DEBG 'watchdog-script' stderr output:
<Deferred at 0x155476456c20 current result: None>

2022-07-05 13:21:43,122 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found


2022-07-05 13:21:43,123 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2022-07-05 13:21:43,123 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2022-07-05 13:21:43,126 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2022-07-05 13:21:44,135 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2022-07-05 13:21:44,142 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2022-07-05 13:35:55,070 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 13:48:33,559 DEBG 'watchdog-script' stderr output:
Unhandled error in Deferred:


2022-07-05 13:48:33,566 DEBG 'watchdog-script' stderr output:

Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 858, in _runCallbacks
current.result = callback( # type: ignore[misc]
File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 1338, in _cbDeferred
self.callback(cast(_DeferredListResultListT, self.resultList))
File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 662, in callback
self._startRunCallbacks(result)
File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 764, in _startRunCallbacks
self._runCallbacks()
--- <exception caught here> ---
File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 858, in _runCallbacks
current.result = callback( # type: ignore[misc]
File "/usr/lib/python3.10/site-packages/deluge/ui/web/json_api.py", line 187, in _on_rpc_request_failed
return self._send_response(request, response)
File "/usr/lib/python3.10/site-packages/deluge/ui/web/json_api.py", line 229, in _send_response
response = json.dumps(response)
File "/usr/lib/python3.10/json/__init__.py", line 231, in dumps
return _default_encoder.encode(obj)
File "/usr/lib/python3.10/json/encoder.py", line 199, in encode
chunks = self.iterencode(o, _one_shot=True)
File "/usr/lib/python3.10/json/encoder.py", line 257, in iterencode
return _iterencode(o, 0)
File "/usr/lib/python3.10/json/encoder.py", line 179, in default
raise TypeError(f'Object of type {o.__class__.__name__} '
builtins.TypeError: Object of type Failure is not JSON serializable


2022-07-05 13:48:33,566 DEBG 'watchdog-script' stderr output:
Unhandled error in Deferred:


Traceback (most recent call last):
Failure: deluge.error.AddTorrentError: Torrent already in session (31f39e3afe7c418ea6c10ea1b650e7d6d00680cf).



2022-07-05 13:50:55,508 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 14:05:55,940 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 14:20:56,368 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 14:35:56,819 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 14:50:57,248 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 15:05:57,681 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 15:20:58,114 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 15:35:58,547 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 15:50:58,982 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 16:05:59,411 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 16:20:59,842 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 16:36:00,280 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 16:51:00,722 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 17:06:01,162 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 17:21:01,598 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 17:36:02,030 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 17:51:02,466 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 18:06:02,906 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 18:21:03,339 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 18:36:03,769 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 18:51:04,211 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 19:06:04,651 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 19:21:05,082 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 19:36:05,508 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 19:51:05,942 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 20:06:06,374 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 20:21:06,802 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 20:36:07,231 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 20:51:07,671 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 21:06:08,107 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 21:21:08,541 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 21:36:08,975 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 21:51:09,409 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 22:06:09,831 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 22:21:10,268 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 22:36:10,687 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 22:51:11,108 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 23:06:11,538 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 23:21:11,967 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 23:36:12,400 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 23:51:12,830 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 00:06:13,259 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 00:21:13,688 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 00:36:14,117 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 00:51:14,557 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 01:06:14,992 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 01:21:15,428 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 01:36:15,858 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 01:51:16,292 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 02:06:16,721 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 02:21:17,155 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 02:36:17,582 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 02:51:18,014 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 03:06:18,453 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 03:21:18,909 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 03:36:19,358 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 03:51:19,801 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 04:06:20,239 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 04:21:20,683 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 04:36:21,120 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 04:51:21,553 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 05:06:21,985 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 05:21:22,417 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 05:36:22,850 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 05:51:23,289 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 06:06:23,717 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 06:21:24,144 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 06:36:24,580 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 06:51:25,015 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 07:06:25,443 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 07:21:25,871 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 07:36:26,310 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 07:51:26,742 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 08:06:27,191 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 08:21:27,624 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 08:36:28,062 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 08:51:28,496 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 09:06:28,925 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 09:21:29,357 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 09:36:29,791 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 09:51:30,227 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 10:06:30,658 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 10:21:31,089 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 10:36:31,525 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 10:51:31,956 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

 

Link to comment
2 hours ago, Flyinace2000 said:

@Antimarkovnikov

 

I had the same problem over the weekend.  I solved it by switching VPN endpoints to one of the Canada servers (Montreal I think).  I'm also using WireGuard instead of OpenVPN.

Changing from OpenVPN to WireGuard worked for me.  Although I had to change my LAN_NETWORK setting to 192.168.0.0/24 to get the WebUI to show up after that.

Link to comment

I wanted to continue the issue I'm having with DelugeVPN here.

 

 

I rebooted the unRaid server 3 times but that didn't completely fix the issue.  I'm able to download but it seems to only allow 1 peer per torrent.  I changed the PIA wireguard endpoint from ca-toronto.privacy.network to ca-montreal.privacy.network but get the same results.  

 

Is this an issue with my configurations or is it an issue with PIA?  Thanks.

 

Capture03.thumb.PNG.b69655b922385191a7fbfdab4fa66821.PNG

Link to comment
Posted (edited)
On 7/6/2022 at 1:05 PM, Antimarkovnikov said:

I'm having a issue with Deluge VPN.  Right now all my torrents are not updating their trackers and are sitting at no seeders or peers.  I use PIA and have tried connecting to different ovpn servers and haven't had any luck.  Here's the current log for the docker.

 

2022-07-05 13:21:26,373 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'tun0'
[info] Deluge key 'outgoing_interface' will have a new value 'tun0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-07-05 13:21:26,854 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of '51cb5aaae02ac52ca9d32c0434a98e12d4fac639'
[info] Deluge key 'default_daemon' will have a new value '51cb5aaae02ac52ca9d32c0434a98e12d4fac639'
[info] Writing changes to Deluge config file '/config/web.conf'...

2022-07-05 13:21:27,589 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2022-07-05 13:21:27,923 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2022-07-05 13:21:32,721 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2022-07-05 13:21:32,721 DEBG 'watchdog-script' stderr output:
<Deferred at 0x146235b76d10 current result: None>

2022-07-05 13:21:37,825 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (44187, 44187)
Configuration value successfully updated.

2022-07-05 13:21:37,825 DEBG 'watchdog-script' stderr output:
<Deferred at 0x14ffe7286b60 current result: None>

2022-07-05 13:21:42,935 DEBG 'watchdog-script' stderr output:
<Deferred at 0x155476456c20 current result: None>

2022-07-05 13:21:43,122 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found


2022-07-05 13:21:43,123 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2022-07-05 13:21:43,123 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2022-07-05 13:21:43,126 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2022-07-05 13:21:44,135 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2022-07-05 13:21:44,142 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2022-07-05 13:35:55,070 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 13:48:33,559 DEBG 'watchdog-script' stderr output:
Unhandled error in Deferred:


2022-07-05 13:48:33,566 DEBG 'watchdog-script' stderr output:

Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 858, in _runCallbacks
current.result = callback( # type: ignore[misc]
File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 1338, in _cbDeferred
self.callback(cast(_DeferredListResultListT, self.resultList))
File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 662, in callback
self._startRunCallbacks(result)
File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 764, in _startRunCallbacks
self._runCallbacks()
--- <exception caught here> ---
File "/usr/lib/python3.10/site-packages/twisted/internet/defer.py", line 858, in _runCallbacks
current.result = callback( # type: ignore[misc]
File "/usr/lib/python3.10/site-packages/deluge/ui/web/json_api.py", line 187, in _on_rpc_request_failed
return self._send_response(request, response)
File "/usr/lib/python3.10/site-packages/deluge/ui/web/json_api.py", line 229, in _send_response
response = json.dumps(response)
File "/usr/lib/python3.10/json/__init__.py", line 231, in dumps
return _default_encoder.encode(obj)
File "/usr/lib/python3.10/json/encoder.py", line 199, in encode
chunks = self.iterencode(o, _one_shot=True)
File "/usr/lib/python3.10/json/encoder.py", line 257, in iterencode
return _iterencode(o, 0)
File "/usr/lib/python3.10/json/encoder.py", line 179, in default
raise TypeError(f'Object of type {o.__class__.__name__} '
builtins.TypeError: Object of type Failure is not JSON serializable


2022-07-05 13:48:33,566 DEBG 'watchdog-script' stderr output:
Unhandled error in Deferred:


Traceback (most recent call last):
Failure: deluge.error.AddTorrentError: Torrent already in session (31f39e3afe7c418ea6c10ea1b650e7d6d00680cf).



2022-07-05 13:50:55,508 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 14:05:55,940 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 14:20:56,368 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 14:35:56,819 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 14:50:57,248 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 15:05:57,681 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 15:20:58,114 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 15:35:58,547 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 15:50:58,982 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 16:05:59,411 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 16:20:59,842 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 16:36:00,280 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 16:51:00,722 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 17:06:01,162 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 17:21:01,598 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 17:36:02,030 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 17:51:02,466 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 18:06:02,906 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 18:21:03,339 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 18:36:03,769 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 18:51:04,211 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 19:06:04,651 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 19:21:05,082 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 19:36:05,508 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 19:51:05,942 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 20:06:06,374 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 20:21:06,802 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 20:36:07,231 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 20:51:07,671 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 21:06:08,107 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 21:21:08,541 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 21:36:08,975 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 21:51:09,409 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 22:06:09,831 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 22:21:10,268 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 22:36:10,687 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 22:51:11,108 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 23:06:11,538 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 23:21:11,967 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 23:36:12,400 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-05 23:51:12,830 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 00:06:13,259 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 00:21:13,688 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 00:36:14,117 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 00:51:14,557 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 01:06:14,992 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 01:21:15,428 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 01:36:15,858 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 01:51:16,292 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 02:06:16,721 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 02:21:17,155 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 02:36:17,582 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 02:51:18,014 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 03:06:18,453 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 03:21:18,909 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 03:36:19,358 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 03:51:19,801 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 04:06:20,239 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 04:21:20,683 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 04:36:21,120 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 04:51:21,553 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 05:06:21,985 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 05:21:22,417 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 05:36:22,850 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 05:51:23,289 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 06:06:23,717 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 06:21:24,144 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 06:36:24,580 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 06:51:25,015 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 07:06:25,443 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 07:21:25,871 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 07:36:26,310 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 07:51:26,742 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 08:06:27,191 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 08:21:27,624 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 08:36:28,062 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 08:51:28,496 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 09:06:28,925 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 09:21:29,357 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 09:36:29,791 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 09:51:30,227 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 10:06:30,658 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 10:21:31,089 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 10:36:31,525 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

2022-07-06 10:51:31,956 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44187'

 

 

I'm battling what seems to be the same issue. Using PIA and OpenVPN. I've switched OVPN .conf files for endpoints but no luck.

 

The /mnt/user/appdata/binhex-delugevpn/deluged.log file states this in every container restart. These are the only log entries I can see in either my container logs or in my pfsense logs that are pointing to any sort of error.  pfsense actually doesn't show anything being blocked and I haven't made any firewall changes in ... jeez, months:

 

[19:57:15 [INFO    ][deluge.core.rpcserver         :179 ] Deluge Client connection made from: 127.0.0.1:42028
19:57:15 [INFO    ][deluge.core.rpcserver         :205 ] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
19:57:16 [INFO    ][deluge.core.rpcserver         :179 ] Deluge Client connection made from: 127.0.0.1:42030
19:57:17 [INFO    ][deluge.core.rpcserver         :205 ] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
19:57:18 [INFO    ][deluge.core.rpcserver         :179 ] Deluge Client connection made from: 127.0.0.1:36762
19:57:18 [INFO    ][deluge.core.rpcserver         :205 ] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
19:57:19 [INFO    ][deluge.core.rpcserver         :179 ] Deluge Client connection made from: 127.0.0.1:36770

 

I've changed from Austria to Switzerland and still the same result. But I don't think the VPN is the issue here. The startup logs indicate that the VPN is working. The startup logs indicate that amazonaws returns an address that I expect (meaning, not my own). The container itself has internet access.

Deluge accepts download requests from Prowlarr, etc.

 

Deluge just ... never actually starts downloading anything.

 

This all started in the last few days. Was working fine last week (and indeed, for years up until maybe this past weekend).

 

UPDATE - RESOLVED

I have no idea how or why, but for some reason my binhex-delugevpn container ended up with TWO port definitions pointing to port 58946. The container definitions explicitly called out each line as "Host Port 3" as 'Port 58946' and "Host Port 4" with the same port address. Normally this does not allow the container to start because of a port conflict. Yet, somehow, it did.

 

I removed the "Host Port 4" line in my docker compose instructions via the UnRAID web GUI and now things are ticking along just fine. Note that you should NOT do this unless you see a duplicate entry and 'Host Port 4' is a duplicate of 'Host Port 3'.  Curious that the container still started with duplicate port entries in the same container and Docker didn't at least throw a WARN.

 

I ... I swear I didn't do this myself. I don't run any docker-compose scripts or commands outside of the UnRAID GUI. I tinker on other systems. I largely leave this server sitting in my network closet and only connect to it to add things to the DL list.

 

Like Anton from the TV Show 'Silicon Valley', my server:

Quote

"Grimly does his work, then he sits motionless until it's time to work again. We could all take a page from his book."

 

Anyway, if anyone else here is having issues with this container downloading files yet otherwise successfully running, take a look in your configuration and ensure you don't have any extra "Host Port" lines or other duplicate entries.

Edited by jaylo123
Added note about when issue was noticed; trimmed down my ramblings.
Link to comment
Posted (edited)
On 7/6/2022 at 2:05 PM, Antimarkovnikov said:

I'm having a issue with Deluge VPN.  Right now all my torrents are not updating their trackers and are sitting at no seeders or peers.  I use PIA and have tried connecting to different ovpn servers and haven't had any luck.  Here's the current log for the docker.

 

I just started having this issue as well a couple of days ago too.  I ran into the same issue as @jaylo123 with the duplicate host 4 port, and removing it didn't help in my case.  What I noticed was in DelugeVPN, if you highlight an entry, go to the options tab, then click "Edit Trackers", the list is blank (Edit: you can also just right click, Edit Trackers)!!  So if you're pasting in or using Radarr/Sonarr that passes a magnet link to DelugeVPN, for some reason the tracker list isn't being parsed correctly.  To fix it, copy/paste the magnet link into a text editor and copy out each of the &tr parameters and add them to your tracker list.  For example:

 

&tr=http%3A%2F%2Ftracker.trackerfix.com%3A80%2Fannounce

 

becomes

 

http://tracker.trackerfix.com:80/announce

 

Not sure how or why this became an issue now, but at least there's a simple workaround.  Hopefully @binhex can take a quick look and see what the source of the issue is.. please.  :)

 

Edited by Wrog
Link to comment

I have been having the same problems as you all for the last week or so. Torrents sit at zero across the board. Tried the above tips with no success. Disabling VPN doesn't work.

 

I also never touch server settings and I have actually been away from work, so I came home to nothing working. I do however have auto update set up so I'm assuming this may be due to a recent update? Hopefully a solution can be found soon because I have been pulling my hair out the last two days trying to make this work.

Link to comment
Mine has the duplicate host port 4 (I just updated to 6.10.3 yesterday - didn't have this issue before then).  Removed port 4 and will see how it does.
It's not a duplicate guys and has been like this for a long time, it's UDP and TCP for the port:-

https://github.com/binhex/docker-templates/blob/42c31fcabb842e1b51e26935a6a9198a857f2f3e/binhex/delugevpn.xml#L41-L50

Just to be clear, that port can only used if the VPN is turned off, so changing that in any way has no effect when running with the VPN turned on


  • Like 1
Link to comment
Posted (edited)

Recently (past week) a tracker I use started rejecting connection requests with the deluge client saying: "Client calling in as ("-DE" / "Deluge/2.1.0 libtorrent/2.0.6.0") is not allowed, please check the Rules for an allowed client "  

 

The rules state: "Due to release stream issues, Versions 2.x Sourced from their PPA (or docker based on PPA) will not work here"

 

This image is arch based right? So I can't imagine it's coming from the PPA - Did the user agent change recently?  I'm seeing a full string as 

 

"-DE205s-
Deluge/2.1.0 libtorrent/2.0.6.0"

 

Which seems fine? 

Edited by bbeecher
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.