[Support] binhex - DelugeVPN


Recommended Posts

12 minutes ago, binhex said:

 

if your lan network is 10.0.1.0/24 (is it?) then set your deluge network to something other than that, e.g. 10.0.2.0/24,

Guess I’m not sure what you mean by “deluge network”? Are you talking about the br1 settings in settings>docker or the network type in Deluge docker configuration?

Link to comment
4 minutes ago, wgstarks said:

Guess I’m not sure what you mean by “deluge network”? Are you talking about the br1 settings in settings>docke

 

sorry that is a bit ambiguous, i meant the definition of the br1 network, so br1 network should be 10.0.2.0/24 (or anything other than the same as your LAN), in short delugevpn needs to be able to differentiate between your LAN and the internal netnetwork (aka br1) as used by docker in bridge mode.

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

 

sorry that is a bit ambiguous, i meant the definition of the br1 network, so br1 network should be 10.0.2.0/24 (or anything other than the same as your LAN), in short delugevpn needs to be able to differentiate between your LAN and the internal netnetwork (aka br1) as used by docker in bridge mode.

Alright, I get that I think. And then set a static IP of 10.0.2.200 and 10.0.1.0/24 in the LAN_NETWORK Deluge configuration?

Link to comment
1 minute ago, wgstarks said:

Alright, I get that I think. And then set a static IP of 10.0.2.200 and 10.0.1.0/24 in the LAN_NETWORK Deluge configuration?

 

exactly, yes.

 

im actually quite surprised you could even define a overlapping network for br1, god knows what sort of issues that would give you, doesn't sound good to me (ip conflicts most prob)  so def needs fixing up.

Link to comment
Just now, binhex said:

 

exactly, yes.

 

im actually quite surprised you could even define a overlapping network for br1, god knows what sort of issues that would give you, doesn't sound good to me (ip conflicts most prob)  so def needs fixing up.

That was actually the suggested setting ie it was already present in the settings and I put a check mark in the box.

Link to comment
1 minute ago, wgstarks said:

That was actually the suggested setting ie it was already present in the settings and I put a check mark in the box.

 

hmm sounds like a bug in the unraid ui then to me, unless the idea is to give you a starting point, as in "here's your lan network, now create a new one thats similar by tweaking the octet".

Link to comment
Just now, binhex said:

 

hmm sounds like a bug in the unraid ui then to me, unless the idea is to give you a starting point, as in "here's your lan network, now create a new one thats similar by tweaking the octet".

IDK. It’s an optional setting. Maybe the idea was to give an example? Probably for most people 10.x.x.x would be completely different from their LAN.

Link to comment
6 hours ago, wgstarks said:

Alright, I get that I think. And then set a static IP of 10.0.2.200 and 10.0.1.0/24 in the LAN_NETWORK Deluge configuration?

 

5 hours ago, binhex said:

 

exactly, yes.

 

im actually quite surprised you could even define a overlapping network for br1, god knows what sort of issues that would give you, doesn't sound good to me (ip conflicts most prob)  so def needs fixing up.

This isn’t going to work. I can’t change the subnet.

0482F6ED-CA17-47CE-8269-9B16E7094D28.thumb.png.d7962e95685b8b0ce95f4e919da71ae5.png

 

I am either use 10.0.1.0 or 10.0.1.128. I tried just not setting a custom pool at all but that failed too.

Link to comment
This isn’t going to work. I can’t change the subnet.
0482F6ED-CA17-47CE-8269-9B16E7094D28.thumb.png.d7962e95685b8b0ce95f4e919da71ae5.png
 
I am either use 10.0.1.0 or 10.0.1.128. I tried just not setting a custom pool at all but that failed too.
Ah I see, just had a play myself. So I only have a single NIC in my system so I can't try this, but can you not define additional networks for your other NICs and then use this for br1 or even create another bridge adapter?

I have to ask as well, why the heck do you want to do all this? What does it really give you over running it in 'normal' mode? I could understand it if your internet connection is Gbit

Sent from my SM-G935F using Tapatalk

Link to comment
2 minutes ago, binhex said:

Ah I see, just had a play myself. So I only have a single NIC in my system so I can't try this, but can you not define additional networks for your other NICs and then use this for br1 or even create another bridge adapter?

I have to ask as well, why the heck do you want to do all this? What does it really give you over running it in 'normal' mode? I could understand it if your internet connection is Gbit

Sent from my SM-G935F using Tapatalk
 

My primary goal is just to make use of my second (unused) nic. Figured if i could move torrents to the second nic it might help relieve port congestion.

Link to comment

searching this thread didn't reveal the answer to me, so I want to ask, why is community applications giving me 2 errors, which are almost identical...

 

Docker Application delugevpn, Container Port 58946 not found or changed on installed application

Docker Application binhex-delugevpn, Container Port 58946 not found or changed on installed application

 

I'm only running the binhex-delugevpn docker on this machine (I probably had regular delugevpn a LONG time ago, but no longer.)

 

I checked and the template seems to have included port 58846, but not 58946, and I did not remap it.  I asked about this in the community applications thread, but was suggested to ask here about it.

 

I don't really care about the error, but I'm confused why it's there (repeatedly) and how to 'fix' it so that I'm not getting warnings about errors that seem irrelevant.

 

I've read this port is necessary if not running with VPN, so I suppose I could delete it, but again, my template only shows 58846, and the error is 58946, so I suspect it's just as easy to get more errors if I remove this port.  I could add the 58946 port to the docker, but I'm not sure that would help either.

 

Anyway, just trying to 'fix' all errors that fix common errors is showing me, and this is the last one.  Any help is much appreciated.

Link to comment
3 hours ago, wgstarks said:

When I try to start the docker I get a pop up saying “no such container”???

Ok. I deleted and re-installed the docker and appdata folder. The template has changed so there were a few surprises. PIA isn't automatic anymore I guess. Had to download and install the pia netherlands ovpn file to get the docker started. Now it shows that it is started but I can't access the webUI and I don't see any network activity.

 

Docker log-



ErrorWarningSystemArrayLogin

Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2018-01-19 17:47:51.810764 [info] Host is running unRAID
2018-01-19 17:47:51.828269 [info] System information Linux 67cd571490c9 4.14.13-unRAID #1 SMP PREEMPT Wed Jan 10 10:27:09 PST 2018 x86_64 GNU/Linux
2018-01-19 17:47:51.847997 [info] PUID defined as '99'
2018-01-19 17:47:51.868696 [info] PGID defined as '100'
2018-01-19 17:47:51.905167 [info] UMASK defined as '000'
2018-01-19 17:47:51.924505 [info] Setting permissions recursively on volume mappings...
2018-01-19 17:47:52.191873 [info] VPN_ENABLED defined as 'yes'
2018-01-19 17:47:52.215120 [crit] No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting...
Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2018-01-19 17:48:09.456351 [info] Host is running unRAID
2018-01-19 17:48:09.473583 [info] System information Linux 67cd571490c9 4.14.13-unRAID #1 SMP PREEMPT Wed Jan 10 10:27:09 PST 2018 x86_64 GNU/Linux
2018-01-19 17:48:09.492912 [info] PUID defined as '99'
2018-01-19 17:48:09.512868 [info] PGID defined as '100'
2018-01-19 17:48:09.550533 [info] UMASK defined as '000'
2018-01-19 17:48:09.569677 [info] Permissions already set for volume mappings
2018-01-19 17:48:09.591203 [info] VPN_ENABLED defined as 'yes'
2018-01-19 17:48:09.612453 [crit] No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting...
Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2018-01-19 17:48:21.813108 [info] Host is running unRAID
2018-01-19 17:48:21.830235 [info] System information Linux 67cd571490c9 4.14.13-unRAID #1 SMP PREEMPT Wed Jan 10 10:27:09 PST 2018 x86_64 GNU/Linux
2018-01-19 17:48:21.849746 [info] PUID defined as '99'
2018-01-19 17:48:21.869899 [info] PGID defined as '100'
2018-01-19 17:48:21.910129 [info] UMASK defined as '000'
2018-01-19 17:48:21.928933 [info] Permissions already set for volume mappings
2018-01-19 17:48:21.949938 [info] VPN_ENABLED defined as 'yes'
2018-01-19 17:48:21.970888 [crit] No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting...
Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2018-01-19 18:04:08.186080 [info] Host is running unRAID
2018-01-19 18:04:08.205915 [info] System information Linux 67cd571490c9 4.14.13-unRAID #1 SMP PREEMPT Wed Jan 10 10:27:09 PST 2018 x86_64 GNU/Linux
2018-01-19 18:04:08.225620 [info] PUID defined as '99'
2018-01-19 18:04:08.246674 [info] PGID defined as '100'
2018-01-19 18:04:08.286041 [info] UMASK defined as '000'
2018-01-19 18:04:08.305234 [info] Permissions already set for volume mappings
2018-01-19 18:04:08.329381 [info] VPN_ENABLED defined as 'yes'
2018-01-19 18:04:08.352429 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/Netherlands.ovpn
dos2unix: converting file /config/openvpn/Netherlands.ovpn to Unix format...
2018-01-19 18:04:08.373597 [info] VPN remote line defined as 'nl.privateinternetaccess.com 1198'
2018-01-19 18:04:08.394204 [info] VPN_REMOTE defined as 'nl.privateinternetaccess.com'
2018-01-19 18:04:08.414392 [info] VPN_PORT defined as '1198'
2018-01-19 18:04:08.434772 [info] VPN_PROTOCOL defined as 'udp'
2018-01-19 18:04:08.454870 [info] VPN_DEVICE_TYPE defined as 'tun'
2018-01-19 18:04:08.478175 [info] VPN_PROV defined as 'pia'
2018-01-19 18:04:08.498937 [info] LAN_NETWORK defined as '10.0.1.0/24'
2018-01-19 18:04:08.521418 [info] NAME_SERVERS defined as '209.222.18.222,37.235.1.174,8.8.8.8,209.222.18.218,37.235.1.177,8.8.4.4'
2018-01-19 18:04:08.542362 [info] VPN_USER defined as 'redacted'
2018-01-19 18:04:08.562650 [info] VPN_PASS defined as 'redacted'
2018-01-19 18:04:08.585077 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2018-01-19 18:04:08.605051 [info] STRICT_PORT_FORWARD defined as 'yes'
2018-01-19 18:04:08.625644 [info] ENABLE_PRIVOXY defined as 'no'
2018-01-19 18:04:08.643373 [info] Setting permissions on files/folders inside container...
2018-01-19 18:04:08.666403 [info] Starting Supervisor...
2018-01-19 18:04:08,793 CRIT Set uid to user 0
2018-01-19 18:04:08,793 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2018-01-19 18:04:08,795 INFO supervisord started with pid 7
2018-01-19 18:04:09,797 INFO spawned: 'start-script' with pid 131
2018-01-19 18:04:09,798 INFO spawned: 'deluge-script' with pid 132
2018-01-19 18:04:09,799 INFO spawned: 'deluge-web-script' with pid 133
2018-01-19 18:04:09,800 INFO spawned: 'privoxy-script' with pid 134
2018-01-19 18:04:09,800 INFO reaped unknown pid 8
2018-01-19 18:04:09,803 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2018-01-19 18:04:09,804 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-01-19 18:04:09,804 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-01-19 18:04:09,804 INFO success: deluge-web-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-01-19 18:04:09,804 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-01-19 18:04:09,804 DEBG 'deluge-script' stdout output:
[info] Deluge config file doesn't exist, copying default...

2018-01-19 18:04:09,806 DEBG 'privoxy-script' stdout output:
[info] Privoxy set to disabled

2018-01-19 18:04:09,807 DEBG fd 22 closed, stopped monitoring <POutputDispatcher at 23041927756400 for <Subprocess at 23041927754456 with name privoxy-script in state RUNNING> (stdout)>
2018-01-19 18:04:09,807 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 23041927756832 for <Subprocess at 23041927754456 with name privoxy-script in state RUNNING> (stderr)>
2018-01-19 18:04:09,807 INFO exited: privoxy-script (exit status 0; expected)
2018-01-19 18:04:09,807 DEBG received SIGCLD indicating a child quit
2018-01-19 18:04:09,816 DEBG 'deluge-script' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2018-01-19 18:04:09,839 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2018-01-19 18:04:09,841 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2018-01-19 18:04:09,843 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2018-01-19 18:04:09,846 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2018-01-19 18:04:09,848 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2018-01-19 18:04:09,850 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2018-01-19 18:04:09,853 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2018-01-19 18:04:09,903 DEBG 'start-script' stdout output:
[info] Adding 10.0.1.0/24 as route via docker eth0

2018-01-19 18:04:09,904 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2018-01-19 18:04:09,904 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0
10.0.1.0/24 via 172.17.0.1 dev eth0
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.7

2018-01-19 18:04:09,904 DEBG 'start-script' stdout output:
--------------------

2018-01-19 18:04:09,908 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2018-01-19 18:04:09,920 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2018-01-19 18:04:10,079 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2018-01-19 18:04:10,080 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A INPUT -s 10.0.1.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -d 10.0.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2018-01-19 18:04:10,080 DEBG 'start-script' stdout output:
--------------------

2018-01-19 18:04:10,080 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2018-01-19 18:04:10,108 DEBG 'start-script' stdout output:
Options error: --ca fails with 'ca.rsa.2048.crt': No such file or directory (errno=2)
Options error: --crl-verify fails with 'crl.rsa.2048.pem': No such file or directory (errno=2)
Fri Jan 19 18:04:10 2018 WARNING: file 'credentials.conf' is group or others accessible
Options error: Please correct these errors.
Use --help for more information.

2018-01-19 18:04:10,108 DEBG 'start-script' stdout output:
[info] OpenVPN started

 

supervisord.log

 

 

EDIT: NEVERMIND I wasn't even thinking about backups. Restored from an app data backup and now everything seems to be working. I think I'll just leave everything alone for now. :D

Edited by wgstarks
Link to comment
On 1/19/2018 at 1:05 PM, JustinChase said:

searching this thread didn't reveal the answer to me, so I want to ask, why is community applications giving me 2 errors, which are almost identical...

 

Docker Application delugevpn, Container Port 58946 not found or changed on installed application

Docker Application binhex-delugevpn, Container Port 58946 not found or changed on installed application

 

I'm only running the binhex-delugevpn docker on this machine (I probably had regular delugevpn a LONG time ago, but no longer.)

 

I checked and the template seems to have included port 58846, but not 58946, and I did not remap it.  I asked about this in the community applications thread, but was suggested to ask here about it.

 

I don't really care about the error, but I'm confused why it's there (repeatedly) and how to 'fix' it so that I'm not getting warnings about errors that seem irrelevant.

 

I've read this port is necessary if not running with VPN, so I suppose I could delete it, but again, my template only shows 58846, and the error is 58946, so I suspect it's just as easy to get more errors if I remove this port.  I could add the 58946 port to the docker, but I'm not sure that would help either.

 

Anyway, just trying to 'fix' all errors that fix common errors is showing me, and this is the last one.  Any help is much appreciated.

 

I had the same issue and just added port 58946 to the docker, which fixed the problem. But yes, also curious why its not included in the template

Link to comment
 
I had the same issue and just added port 58946 to the docker, which fixed the problem. But yes, also curious why its not included in the template
I can confirm that this worked for me also. I suspect this port was added to the template after I originally installed the docker. fix common problems checks against the current template, which includes this additional port.

Sent from my HTC6545LVW using Tapatalk

Link to comment

Does anyone successfully use the Newshosting VPN service with Deluge? I have things setup and downloading correctly but nothing uploads. The torrents say they are seeding but they don't connect to any peers or upload. Spaceinvaders YouTube video uses PIA and limits the server to the Netherlands. He mentions that it needs to be a server that supports port forwarding. I've tried looking but haven't been able to find anything about Newshosting's VPN servers and port forwarding.  

 

Thanks!

Link to comment
Does anyone successfully use the Newshosting VPN service with Deluge? I have things setup and downloading correctly but nothing uploads. The torrents say they are seeding but they don't connect to any peers or upload. Spaceinvaders YouTube video uses PIA and limits the server to the Netherlands. He mentions that it needs to be a server that supports port forwarding. I've tried looking but haven't been able to find anything about Newshosting's VPN servers and port forwarding.  
 
Thanks!
If there is no mention then I suspect that provider doesn't offer port forwarding, switch to pia or airvpn (recommended providers)

Sent from my SM-G935F using Tapatalk

Link to comment

I had to recreate  container that I was using.  I've used the same script i originally used (attached) after deleting the original container.  Everything seems to go fine during creation (see attached log) but I cannot access the instance of Deluge running in the container.  (192.168.200.210:58081 not found) I've changed the name of the container, the ports, an I don't have a firewall running, but still I am unable to connect to the new container.  Can anyone suggest how I can proceed to get this to work?  Thanks.

delugevpn.txt

delugelog.txt

Link to comment

With the recent update to 6.4.0, I decided to change the dockers over to their own IPs.  After some initial confusion, I have been able to get all the dockers working fine except for the Web UI of my binhex-delugevpn and binhex-sabnzbdvpn dockers.  The odd thing is that I know the dockers are running.  For example, with the deluge docker, I can connect to it using the deluge client on my desktop.  I can use also privoxy without issue and other dockers such as radarr and sonarr report that they can connect to them fine.  Its just the WebUI will now no longer come up.  For all the others, the issue revolved around something in the docker trying to communicate with the unraid host, which is prohibited by macvlan.

 

Any thoughts on what might be happening?

Link to comment
14 minutes ago, mattekure said:

Any thoughts on what might be happening?

I tried this a few days ago. You’ll find the posts if you look back a page or two.

 

TL;DR- I could ping between the various dockers. I could connect to Deluge via the thin client but not from Sonarr, Radarr or webUI. Never could get it to work and finally gave up on it.

 

If you do get this to work please post your process.

Link to comment

So I just got a nastygram from my ISP, and I'm wondering how in the heck it happened. I shut it down for now but plan to bring this back online.

 

I've confirmed my IP and DNS are not leaking via ipleak, I am getting a good VPN connection per the logs, and I've confirmed via magnet link from ipleak that my external IP matches the logs. Is there anything else that I can do to test for leaks? I'm not entirely sure how it happened.

 

Is there any way to add a killswitch or is this already a part of the build? Wanting to be as safe as possible considering the circumstances.

 

TIA.

Link to comment
9 minutes ago, kreene1987 said:

So I just got a nastygram from my ISP, and I'm wondering how in the heck it happened. I shut it down for now but plan to bring this back online.

 

I've confirmed my IP and DNS are not leaking via ipleak, I am getting a good VPN connection per the logs, and I've confirmed via magnet link from ipleak that my external IP matches the logs. Is there anything else that I can do to test for leaks? I'm not entirely sure how it happened.

 

Is there any way to add a killswitch or is this already a part of the build? Wanting to be as safe as possible considering the circumstances.

 

TIA.

 

ok lets get some info for starters:-

 

1. are you using the built in privoxy? if so are you using it for any other torrent clients?

2. how did you download the torrent/magnet link? if its just via browser then did you use privoxy or over your standard connection?

3. what dns are you using for the container?, is it your isp''s dns or the defaults?

4. do you have any other torrent clients running anywhere on your LAN, check there are no other torrent clients running on any other hosts.

5. have you configured deluge to socks proxy?

6. does your vpn provider log?, who is your vpn provider?

 

in answer to your question, yes there is built in protection via iptables, it doesnt matter if the vpn tunnel is up, down or initialising, you are always protected.

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.