[Support] binhex - DelugeVPN


Recommended Posts

1 minute ago, StarsLight said:

 

Tried but I cannot get through after restart the server.... ?

 

Image 1.png

 

if you restart unraid then you need to re-run that command again before you start the container, or put it in the /boot/config/go script so that its executed on boot (what i do)

Link to comment

Hi first post,

Seem to be having problems with this docker. Seen other questions on same problem but I cannot fathom it. Cannot start Deluge with VPN enabled but works OK with VPN disabled. My log file does not seem to have any errors. Passwordis included as it is a public VPN. The ovpn file works ok with other openvpn clienst such as windows and xubuntu.

Probably simple solution. Help appreciated.

supervisord.log

Link to comment

I am trying to setup TransmissionVPN (by activ, based on binhex's VPN code) but I believe here would be the right thread to post about issues, for I don't even get to see the WebGUI and I think it is related to the network side of things.

Docker log

 

Docker settings:

Host Port 1: 9091
Host Port 2: 8118
Host Path 2: /mnt/user/Downloads
Key 1: yes (VPN_ENABLED)
Key 2: $username (VPN_USER)
Key 3: $password (VPN_PASS)
Key 4: $serveraddress (VPN_REMOTE)
Key 5: 1195 (VPN_PORT)
Key 6: PPTP (VPN_PROTOCOL)
Key 7: custom (VPN_PROV)
Key 8: no (ENABLE_PRIVOXY)
Key 9: 192.168.1.0/24 (LAN_NETWORK)
Key 10: 192.168.*.* (WHITELIST)
Key 11: false (DEBUG)
Key 12: 99 (PUID)
Key 13: 100 (PGID)
unRAID Share Path: /mnt/user
AppData Config Path: /mnt/user/appdata/activ-transmissionvpn

 

Notes:

None of the ports stated are portforwared. And yes, the VPN_PORT was changed to 1195 from 1194, because I use OpenVPN-as from LinuxServer.io already, and have 1194 therfore portforwarded.

VPN info has been tested through PTTP on my Windows, and works.

My router IP is set to 192.168.0.1 (was 192.168.178.1 initially, if that matters)

Link to comment

Thanks, I have transferred the post over there.

 

In the meanwhile, I have tried DelugeVPN aswell, I figured it can't hurt.

I cannot seem to access the WebGUI here aswell.

Docker log

 

Same settings/situation as before, except for some things:

Host Port 1: 8112
Host Port 2: 58846
Host Port 3: 58946
Host Port 4: 58946
Host Port 5: 8118
Host Parth 2: /mnt/cache/appdata/data
#(No VPN_REMOTE defined, using a .ovpn file under "/mnt/user/appdata/binhex-delugevpn/openvpn")
Key 4: custom (and tried airvpn aswell) (VPN_PROV)
Key 5: (VPN_OPTIONS)
Key 6: yes (STRICT_PORT_FORWARD)
Key 9: 209.222.18.222,37.235.1.174,8.8.8.8,209.222.18.218,37.235.1.177,8.8.4.4 (NAME_SERVERS) #(Default)
Key 11: 000 (UMASK)
AppData Config Path: /mnt/user/appdata/binhex-delugevpn (/config)

Notes:

I noticed the OpenVPN inside the docker uses 1194 and cannot be changed. Just to make sure, is it an issue that the port is already in use by the OpenVPN-as docker from LinuxServer.io?

Edited by Arndroid
Link to comment
12 minutes ago, Arndroid said:

Thanks, I have transferred the post over there.

 

In the meanwhile, I have tried DelugeVPN aswell, I figured it can't hurt.

I cannot seem to access the WebGUI here aswell.

Docker log

 

Same settings/situation as before, except for some things:


Host Port 1: 8112
Host Port 2: 58846
Host Port 3: 58946
Host Port 4: 58946
Host Port 5: 8118
Host Parth 2: /mnt/cache/appdata/data
#(No VPN_REMOTE defined, using a .ovpn file under "/mnt/user/appdata/binhex-delugevpn/openvpn")
Key 4: custom (and tried airvpn aswell) (VPN_PROV)
Key 5: (VPN_OPTIONS)
Key 6: yes (STRICT_PORT_FORWARD)
Key 9: 209.222.18.222,37.235.1.174,8.8.8.8,209.222.18.218,37.235.1.177,8.8.4.4 (NAME_SERVERS) #(Default)
Key 11: 000 (UMASK)
AppData Config Path: /mnt/user/appdata/binhex-delugevpn (/config)

Notes:

I noticed the OpenVPN inside the docker uses 1194 and cannot be changed. Just to make sure, is it an issue that the port is already in use by the OpenVPN-as docker from LinuxServer.io?

 

wrong username and/or password:-

 

AUTH: Received control message: AUTH_FAILED

the port 1194 is picked up from your openvpn config file, it wont conflict with anything, as this port is used inside the running container, its not exposed to the host.

 

to make things simple follow the newbie guide:-

 

 

Edited by binhex
Link to comment
1 minute ago, binhex said:

 

wrong username and/or password:-

 


AUTH: Received control message: AUTH_FAILED

the port 1194 is picked up from your openvpn config file, it wont conflict with anything, as this port is used inside the running container, its not exposed to the host.

Wow... you're right. O.o

 

Thanks, seems to work now! That went really smooth, I like it.

Link to comment

Hi All,

 

I'm running into what I think is a simple issue that I can't quite resolve. I have a feeling you may want more information, but here's what I see as the crux of my problem:

 

2017-08-23 22:37:26,083 DEBG 'start-script' stdout output:
--------------------

2017-08-23 22:37:26,099 DEBG 'start-script' stdout output:
[warn] 'iptable_mangle' kernel module not available, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID users: Please attempt to load the module by executing the following on your host:- '/sbin/modprobe iptable_mangle'
[info] Ubuntu users: Please attempt to load the module by executing the following on your host:- '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host:- 'insmod /lib/modules/iptable_mangle.ko'

 

This is part of my supervisord.log file, I greatly appreciate any and all suggestions!

Link to comment
3 hours ago, ocrower said:

I'm running into what I think is a simple issue that I can't quite resolve

 

you dont actually state what your simple issue is, but reading between the lines im assuming you cant get access to the deluge web ui outside of your lan right?, if this is the case have you tried running the command suggested in the log at ssh prompt on unraid?:-

 

/sbin/modprobe iptable_mangle

 

Link to comment

Hey guys,

 

Been dabbing my toes into running DelugeVPN on my QNAP.  Keep running into a problem with the iptables on the QNAP, which I guess isn't supported.  I attached my log to give the full picture.  Deluge runs great when I set VPN ENABLED to no.  Thanks in advance.  

 

Quote

2017-08-24 09:51:27.509801 [info] System information Linux 83e048b55025 4.2.8 #1 SMP Thu Jul 27 01:39:07 CST 2017 x86_64 GNU/Linux
2017-08-24 09:51:27.555117 [info] PUID defined as '0'
2017-08-24 09:51:29.484639 [info] PGID defined as '0'
2017-08-24 09:51:29.885210 [info] UMASK defined as '000'
2017-08-24 09:51:29.950655 [info] Permissions already set for volume mappings
2017-08-24 09:51:29.995164 [info] VPN_ENABLED defined as 'yes'
2017-08-24 09:51:30.038584 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/Japan.ovpn
dos2unix: converting file /config/openvpn/Japan.ovpn to Unix format...
2017-08-24 09:51:30.077613 [info] VPN remote line defined as 'japan.privateinternetaccess.com 1198'
2017-08-24 09:51:30.117674 [info] VPN_REMOTE defined as 'japan.privateinternetaccess.com'
2017-08-24 09:51:30.158205 [info] VPN_PORT defined as '1198'
2017-08-24 09:51:30.198848 [info] VPN_PROTOCOL defined as 'udp'
2017-08-24 09:51:30.238963 [info] VPN_DEVICE_TYPE defined as 'tun'
2017-08-24 09:51:30.279925 [info] VPN_PROV defined as 'pia'
2017-08-24 09:51:30.318316 [info] LAN_NETWORK defined as '192.168.1.0/24'
2017-08-24 09:51:30.358915 [info] NAME_SERVERS defined as '8.8.8.8,8.8.4.4'
2017-08-24 09:51:30.397559 [info] VPN_USER defined as 'user'
2017-08-24 09:51:30.436155 [info] VPN_PASS defined as 'pass'
2017-08-24 09:51:30.477393 [warn] VPN_INCOMING_PORT not defined (via -e VPN_INCOMING_PORT), downloads may be slow
2017-08-24 09:51:30.518851 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2017-08-24 09:51:30.555692 [info] STRICT_PORT_FORWARD defined as 'no'
2017-08-24 09:51:30.597187 [info] ENABLE_PRIVOXY defined as 'no'
2017-08-24 09:51:30.633566 [info] Setting permissions on files/folders inside container...
2017-08-24 09:51:30.874485 [info] Starting Supervisor...
2017-08-24 09:51:31,320 CRIT Set uid to user 0
2017-08-24 09:51:31,320 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2017-08-24 09:51:31,324 INFO supervisord started with pid 7
2017-08-24 09:51:32,326 INFO spawned: 'start-script' with pid 133
2017-08-24 09:51:32,328 INFO spawned: 'deluge-script' with pid 134
2017-08-24 09:51:32,329 INFO spawned: 'deluge-web-script' with pid 135
2017-08-24 09:51:32,331 INFO spawned: 'privoxy-script' with pid 136
2017-08-24 09:51:32,332 INFO reaped unknown pid 8
2017-08-24 09:51:32,336 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2017-08-24 09:51:32,337 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-08-24 09:51:32,337 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-08-24 09:51:32,337 INFO success: deluge-web-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-08-24 09:51:32,337 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-08-24 09:51:32,337 DEBG 'deluge-script' stdout output:
[info] Deluge config file already exists, skipping copy
[info] VPN is enabled, checking VPN tunnel local ip is valid

2017-08-24 09:51:32,341 DEBG 'privoxy-script' stdout output:
[info] Privoxy set to disabled

2017-08-24 09:51:32,342 DEBG fd 22 closed, stopped monitoring <POutputDispatcher at 140123225310848 for <Subprocess at 140123225312000 with name privoxy-script in state RUNNING> (stdout)>
2017-08-24 09:51:32,342 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 140123225311136 for <Subprocess at 140123225312000 with name privoxy-script in state RUNNING> (stderr)>
2017-08-24 09:51:32,342 INFO exited: privoxy-script (exit status 0; expected)
2017-08-24 09:51:32,342 DEBG received SIGCLD indicating a child quit
2017-08-24 09:51:32,389 DEBG 'start-script' stdout output:
[info] Default route for container is 10.0.5.1

2017-08-24 09:51:32,393 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2017-08-24 09:51:32,397 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2017-08-24 09:51:32,462 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2017-08-24 09:51:32,463 DEBG 'start-script' stderr output:
RTNETLINK answers: Operation not permitted

2017-08-24 09:51:32,464 DEBG 'start-script' stdout output:
[info] ip route defined as follows...

2017-08-24 09:51:32,464 DEBG 'start-script' stdout output:
--------------------

2017-08-24 09:51:32,465 DEBG 'start-script' stdout output:
default via 10.0.5.1 dev eth0 
10.0.5.0/24 dev eth0 proto kernel scope link src 10.0.5.2 

2017-08-24 09:51:32,465 DEBG 'start-script' stdout output:
--------------------

2017-08-24 09:51:32,469 DEBG 'start-script' stdout output:
[warn] 'iptable_mangle' kernel module not available, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID users: Please attempt to load the module by executing the following on your host:- '/sbin/modprobe iptable_mangle'
[info] Ubuntu users: Please attempt to load the module by executing the following on your host:- '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host:- 'insmod /lib/modules/iptable_mangle.ko'

2017-08-24 09:51:32,495 DEBG 'start-script' stdout output:
[info] Docker network defined as    10.0.5.0/24

2017-08-24 09:51:32,497 DEBG 'start-script' stderr output:
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,500 DEBG 'start-script' stderr output:
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,502 DEBG 'start-script' stderr output:
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,505 DEBG 'start-script' stderr output:
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,508 DEBG 'start-script' stderr output:
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,510 DEBG 'start-script' stderr output:
iptables v1.6.1: 
2017-08-24 09:51:32,511 DEBG 'start-script' stderr output:
can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,519 DEBG 'start-script' stderr output:
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,521 DEBG 'start-script' stderr output:
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,523 DEBG 'start-script' stderr output:
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,525 DEBG 'start-script' stderr output:
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,528 DEBG 'start-script' stderr output:
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,530 DEBG 'start-script' stderr output:
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,533 DEBG 'start-script' stderr output:
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,535 DEBG 'start-script' stderr output:
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,538 DEBG 'start-script' stderr output:
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,544 DEBG 'start-script' stderr output:
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,547 DEBG 'start-script' stderr output:
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,549 DEBG 'start-script' stderr output:
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,550 DEBG 'start-script' stdout output:
[info] iptables defined as follows...

2017-08-24 09:51:32,550 DEBG 'start-script' stdout output:
--------------------

2017-08-24 09:51:32,552 DEBG 'start-script' stderr output:
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2017-08-24 09:51:32,552 DEBG 'start-script' stdout output:
--------------------

2017-08-24 09:51:32,553 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2017-08-24 09:51:32,559 DEBG 'start-script' stdout output:
Thu Aug 24 09:51:32 2017 WARNING: file 'credentials.conf' is group or others accessible
Thu Aug 24 09:51:32 2017 OpenVPN 2.4.1 x86_64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Mar 22 2017
Thu Aug 24 09:51:32 2017 library versions: OpenSSL 1.1.0e  16 Feb 2017, LZO 2.10

2017-08-24 09:51:32,560 DEBG 'start-script' stdout output:
Thu Aug 24 09:51:32 2017 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
[info] OpenVPN started

2017-08-24 09:51:32,562 DEBG 'start-script' stdout output:
Thu Aug 24 09:51:32 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]103.208.220.144:1198
Thu Aug 24 09:51:32 2017 UDP link local: (not bound)
Thu Aug 24 09:51:32 2017 UDP link remote: [AF_INET]103.208.220.144:1198

2017-08-24 09:51:32,662 DEBG 'start-script' stdout output:
Thu Aug 24 09:51:32 2017 [3cba0c632edb4a9b642ba7d2ac0a3f6c] Peer Connection Initiated with [AF_INET]103.208.220.144:1198

2017-08-24 09:51:33,892 DEBG 'start-script' stdout output:
Thu Aug 24 09:51:33 2017 ERROR: Cannot ioctl TUNSETIFF tun: Operation not permitted (errno=1)
Thu Aug 24 09:51:33 2017 Exiting due to fatal error

2017-08-24 09:51:47,584 WARN received SIGTERM indicating exit request
2017-08-24 09:51:47,584 INFO waiting for start-script, deluge-script, deluge-web-script to die
2017-08-24 09:51:48,585 DEBG killing deluge-web-script (pid 135) with signal SIGTERM
2017-08-24 09:51:48,586 DEBG fd 17 closed, stopped monitoring <POutputDispatcher at 140123225309624 for <Subprocess at 140123226324432 with name deluge-web-script in state STOPPING> (stdout)>
2017-08-24 09:51:48,586 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 140123225310416 for <Subprocess at 140123226324432 with name deluge-web-script in state STOPPING> (stderr)>
2017-08-24 09:51:48,586 INFO stopped: deluge-web-script (terminated by SIGTERM)
2017-08-24 09:51:48,586 DEBG received SIGCLD indicating a child quit
2017-08-24 09:51:48,586 DEBG killing deluge-script (pid 134) with signal SIGTERM
2017-08-24 09:51:48,586 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 140123225311064 for <Subprocess at 140123226321912 with name deluge-script in state STOPPING> (stderr)>
2017-08-24 09:51:48,587 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 140123225311496 for <Subprocess at 140123226321912 with name deluge-script in state STOPPING> (stdout)>
2017-08-24 09:51:48,587 INFO stopped: deluge-script (terminated by SIGTERM)
2017-08-24 09:51:48,587 DEBG received SIGCLD indicating a child quit
2017-08-24 09:51:48,587 DEBG killing start-script (pid 133) with signal SIGTERM
2017-08-24 09:51:48,587 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 140123225310920 for <Subprocess at 140123225310776 with name start-script in state STOPPING> (stdout)>
2017-08-24 09:51:48,587 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 140123225309984 for <Subprocess at 140123225310776 with name start-script in state STOPPING> (stderr)>
2017-08-24 09:51:48,587 INFO stopped: start-script (terminated by SIGTERM)
2017-08-24 09:51:48,587 DEBG received SIGCLD indicating a child quit

 

Link to comment
1 minute ago, Squishinator said:

iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)

 

yep def a permissions issue, you need to allow (no clue on how you do this on qnap) docker to modify iptables for the container, have you tried running the container with the --privileged=true flag ?

Link to comment
7 hours ago, binhex said:

 

you dont actually state what your simple issue is, but reading between the lines im assuming you cant get access to the deluge web ui outside of your lan right?, if this is the case have you tried running the command suggested in the log at ssh prompt on unraid?:-

 


/sbin/modprobe iptable_mangle

 

 

Thanks for your quick response. I apologize for not including more information (as I thought would happen). You are correct that I cannot access the GUI for Deluge or OpenVPN.

 

I'm running this on Ubuntu 16.04 and have attempted to run the "/sbin/modprobe iptable_mangle" command on the host machine as well as within the docker container with no success fixing the issue.

 

Please let me know what additional information would be helpful in getting to the bottom of this error, thank you very much in advance!

Link to comment

Ever since you made your recent changes a month or so ago to the DelugeVPN docker, the WebUI mostly refuses to open.  It tries for a while alternating between "connecting to [ip address of unRAID server]" and "looking up [ip address of unRAID server]" messages and eventually I get a browser "connection was reset" message after about 10 seconds.  About one in four attempts, I could get it to open normally. 

 

Today, I had to blow away docker.img and reinstall all dockers.  I also deleted the appdata folder for delugeVPN before reinstalling so nothing is left over from a prior installation.  Now, the GUI refuses to open every time.  The WebUI on all other installed dockers (seven of them) open without issue.

 

I know this is not a general problem and must have something to do with my configuration, but I am stumped where to look.  What information do you need to help me track down and resolve the issue?

 

UPDATE: just saw your instructions on sending a supervisod,log file.  I opened the log and saw this error for every attempt to open the WebUI:

 

"No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting..."

 

Everything worked before your changes without this step. Is this a new requirement that I have somehow overlooked?  Is this saying I need to get an .ovpn file from PIA?  I guess I have some more reading to do in the forums.  My apologies if I missed something.

Edited by Hoopster
Link to comment

Duh, helps if I RTFM or in this case the FAQ. Hopefully, this will be resolved soon.  I think that until today, I was probably still on the old docker and with the reinstall i need to do things I did not have to do previously to get this properly configured.  I was just expecting it to all be automatic with PIA like before.

 

UPDATE: Problem solved by reading the FAQ  - that's probably why you have one, huh? :D

 

So, if for some reason, I wanted to connect to a different PIA endpoint than the one configured, I replace the current .opvn file (Netherlands) with another, correct?  I see this is no longer configurable in the docker.

Edited by Hoopster
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.