[Support] dyonr - jackettvpn


Recommended Posts

11 hours ago, imJohn said:

Hello I've been using this docker with PIA for a while with no issues and after PIA updated all ovpn files the docker stopped working. I've added a new PIA file and whenever It starts it will constantly restart after hitting the line "[ERROR] Password contains unsupported characters." Issue is it is a very normal password containing only numbers and letters. I've ensured there are no spaces or anything strange in it but it continues to fail. Has anyone else run into this issue and have a solution?

 

log https://pastebin.com/JDXKUWGk

 

This error is caused by the 'WEBUI_PASSWORD' environment variable. Could you verify that your WEBUI_PASSWORD environment variable is set and has no weird special characters that might cause this issue?

I'll also make the error message more clear, so it won't cause confusion if it is the VPN password or WEBUI password.

Link to comment
  • 4 months later...

Hey Dyon, great work on this container. Minor suggestion - would it be possible to roll the DNSUtils package (or at least the portion of it that allows "dig" to work) so that we can validate that we are pulling an IP address associated with our VPN via the container console window? If this is not appropriate or there is a better way to do this, please let me know - still learning here as well. I just want to make sure that I am never leaking my public IP address with this container.

Link to comment
  • 4 months later...

Hi all, 

 

I have to put a new OVPN file in every day otherwise the container stops working. I am very new to this but would love to learn! Any ideas on how to keep the VPN connected? 

 

The logs state:

2022-01-07 11:50:08.718184 [INFO] VPN_TYPE defined as 'openvpn'
2022-01-07 11:50:08.738427 [INFO] OpenVPN config file is found at /config/openvpn/._aus_melbourne-aes-128-cbc-udp-dns.ovpn
2022-01-07 11:51:09.190646 [INFO] VPN_ENABLED defined as 'yes'
2022-01-07 11:51:09.206156 [INFO] The container is currently running iptables v1.8.2 (nf_tables).
2022-01-07 11:51:09.221577 [INFO] LEGACY_IPTABLES is set to ''
2022-01-07 11:51:09.235988 [INFO] Not making any changes to iptables version

 

Thank you :)

Link to comment
17 minutes ago, ICULikeMac said:

Hi all, 

 

I have to put a new OVPN file in every day otherwise the container stops working. I am very new to this but would love to learn! Any ideas on how to keep the VPN connected? 

 

The logs state:

2022-01-07 11:50:08.718184 [INFO] VPN_TYPE defined as 'openvpn'
2022-01-07 11:50:08.738427 [INFO] OpenVPN config file is found at /config/openvpn/._aus_melbourne-aes-128-cbc-udp-dns.ovpn
2022-01-07 11:51:09.190646 [INFO] VPN_ENABLED defined as 'yes'
2022-01-07 11:51:09.206156 [INFO] The container is currently running iptables v1.8.2 (nf_tables).
2022-01-07 11:51:09.221577 [INFO] LEGACY_IPTABLES is set to ''
2022-01-07 11:51:09.235988 [INFO] Not making any changes to iptables version

 

Thank you :)

Try changing the filename from `._aus_melbourne-aes-128-cbc-udp-dns.ovpn` to `aus_melbourne-aes-128-cbc-udp-dns.ovpn` (remove the . and _ in front of it) and try again. Or just rename it to something like 'melbourne.ovpn'.

Link to comment

Thanks so much for your response @Dyon (and for the container). 

 

Werid. There was never a . or _ in front of it that was visible in the GUI so I checked midnight commander and it seems there are always duplicate files. One with the one I rename and one with "._<filename>". 

 

Also confirming credentials.conf (along with melbourne.ovpn) is required in the openvpn folder? So just the two files?

 

As I rename it, it seems to generate a copy with "._" Do you think I should just delete the copy ._ and see how I go? 

 

Thanks again!

 

 

Screen Shot 2022-01-07 at 2.09.27 pm.png

Link to comment
12 hours ago, ICULikeMac said:

Thanks so much for your response @Dyon (and for the container). 

 

Werid. There was never a . or _ in front of it that was visible in the GUI so I checked midnight commander and it seems there are always duplicate files. One with the one I rename and one with "._<filename>". 

 

Also confirming credentials.conf (along with melbourne.ovpn) is required in the openvpn folder? So just the two files?

 

As I rename it, it seems to generate a copy with "._" Do you think I should just delete the copy ._ and see how I go? 

 

Thanks again!

 

 

Screen Shot 2022-01-07 at 2.09.27 pm.png

Just delete the '._' one. Should be fine. The .DS_Store, ._.DS_Store and ._melbourne.ovpn are created because you use a Mac. If you open or edit files in there these files will be generated. If I work on an update for the container, I'll try to add something to ignore those files. But for now, just delete any ._ files in there.

Link to comment
  • 3 months later...

Anyone knows why I have this problem?

I use the same openvpn file for other containers without any issues. 


 

2022-05-05 11:45:08.591877 [INFO] VPN_TYPE defined as 'openvpn'
2022-05-05 11:45:08.609954 [INFO] OpenVPN config file is found at /config/openvpn/airvpn.ovpn
2022-05-05 11:45:10.496504 [INFO] VPN_ENABLED defined as 'yes'
2022-05-05 11:45:10.509973 [INFO] The container is currently running iptables v1.8.7 (nf_tables).
2022-05-05 11:45:10.521766 [INFO] LEGACY_IPTABLES is set to ''
2022-05-05 11:45:10.535643 [INFO] Not making any changes to iptables version

 

Edited by deniax
Link to comment
  • 5 months later...

I have been running jackettvpn for the last year or so, and this last week I have run into an issue.

 

jackettvpn will restart every 10 seconds or so with the error: [ERROR] Network is down, exiting this Docker

 

I noticed that if I do not define LAN_Network with my actual lan network, I could get to webui but wasn't able to successfully test any indexers 

 

This seems to have started happening after I changed my default nic in unraid.

 

Here are my logs

 

dos2unix: converting file /config/openvpn/us_las_vegas.ovpn to Unix format...
2022-10-07 15:03:42.246707 [INFO] VPN remote line defined as 'us-lasvegas.privacy.network 1198'
2022-10-07 15:03:42.283072 [INFO] VPN_REMOTE defined as 'us-lasvegas.privacy.network'
2022-10-07 15:03:42.318004 [INFO] VPN_PORT defined as '1198'
2022-10-07 15:03:42.353312 [INFO] VPN_PROTOCOL defined as 'udp'
2022-10-07 15:03:42.388035 [INFO] VPN_DEVICE_TYPE defined as 'tun0'
2022-10-07 15:03:42.425347 [INFO] LAN_NETWORK defined as '10.10.10.0/24'
2022-10-07 15:03:42.460919 [INFO] NAME_SERVERS defined as '1.1.1.1,1.0.0.1'
2022-10-07 15:03:42.495560 [INFO] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2022-10-07 15:03:42.530211 [INFO] Adding 1.1.1.1 to resolv.conf
2022-10-07 15:03:42.565020 [INFO] Adding 1.0.0.1 to resolv.conf
2022-10-07 15:03:42.595756 [INFO] Starting OpenVPN...
2022-10-07 15:03:42 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning.
2022-10-07 15:03:42 WARNING: file 'credentials.conf' is group or others accessible
2022-10-07 15:03:42 OpenVPN 2.5.1 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on May 14 2021
2022-10-07 15:03:42 library versions: OpenSSL 1.1.1n  15 Mar 2022, LZO 2.10
2022-10-07 15:03:42 CRL: loaded 1 CRLs from file -----BEGIN X509 CRL-----
[REMOVED for forum post]
-----END X509 CRL-----

2022-10-07 15:03:42 TCP/UDP: Preserving recently used remote address: [AF_INET]143.244.48.191:1198
2022-10-07 15:03:42 UDP link local: (not bound)
2022-10-07 15:03:42 UDP link remote: [AF_INET]143.244.48.191:1198
2022-10-07 15:03:42 [losangeles408] Peer Connection Initiated with [AF_INET]143.244.48.191:1198
2022-10-07 15:03:42 TUN/TAP device tun0 opened
2022-10-07 15:03:42 net_iface_mtu_set: mtu 1500 for tun0
2022-10-07 15:03:42 net_iface_up: set tun0 up
2022-10-07 15:03:42 net_addr_v4_add: 10.3.112.183/24 dev tun0
2022-10-07 15:03:42 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
2022-10-07 15:03:42 Initialization Sequence Completed
2022-10-07 15:03:43.964770 [INFO] Docker network defined as 172.17.0.0/16
2022-10-07 15:03:44.006199 [INFO] Adding 10.10.10.0/24 as route via docker eth0
2022-10-07 15:03:44.041705 [INFO] ip route defined as follows...
--------------------
0.0.0.0/1 via 10.3.112.1 dev tun0 
default via 172.17.0.1 dev eth0 
10.3.112.0/24 dev tun0 proto kernel scope link src 10.3.112.183 
10.10.10.0/24 via 172.17.0.1 dev eth0 
128.0.0.0/1 via 10.3.112.1 dev tun0 
143.244.48.191 via 172.17.0.1 dev eth0 
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2 
--------------------
iptable_mangle         16384  1
ip_tables              28672  3 iptable_filter,iptable_nat,iptable_mangle
x_tables               45056  17 ip6table_filter,xt_conntrack,iptable_filter,ip6table_nat,nft_compat,xt_tcpudp,xt_addrtype,xt_CHECKSUM,xt_nat,ip6_tables,ipt_REJECT,ip_tables,iptable_nat,ip6table_mangle,xt_MASQUERADE,iptable_mangle,xt_mark
2022-10-07 15:03:44.084100 [INFO] iptable_mangle support detected, adding fwmark for tables
2022-10-07 15:03:44.213293 [INFO] iptables defined as follows...
--------------------
-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 9117 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 9117 -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 9117 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9117 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
--------------------
2022-10-07 15:03:44.270441 [INFO] A group with PGID 100 already exists in /etc/group, nothing to do.
2022-10-07 15:03:44.305489 [INFO] An user with PUID 99 already exists in /etc/passwd, nothing to do.
2022-10-07 15:03:44.338014 [INFO] UMASK defined as '002'
2022-10-07 15:03:44.477298 [WARNING] There is no password set via Jackett's web interface or as an environment variable!
2022-10-07 15:03:44.508562 [WARNING] Anyone on your network could access Jackett without authentication!
2022-10-07 15:03:44.538196 [WARNING] Or even the whole world if you did port-fortwarding!
2022-10-07 15:03:44.568537 [WARNING] It's adviced to set one via either the web interface or as environment variable
2022-10-07 15:03:44.598812 [INFO] Starting Jackett daemon...
Logging to /config/Jackett/Logs/log.txt.
2022-10-07 15:03:45.645209 [INFO] Started Jackett daemon successfully...
2022-10-07 15:03:45.648701 [INFO] Jackett PID: 204
2022-10-07 15:03:45.683864 [ERROR] Network is down, exiting this Docker

 

Link to comment
53 minutes ago, xcsascii said:

I have been running jackettvpn for the last year or so, and this last week I have run into an issue.

 

jackettvpn will restart every 10 seconds or so with the error: [ERROR] Network is down, exiting this Docker

 

I noticed that if I do not define LAN_Network with my actual lan network, I could get to webui but wasn't able to successfully test any indexers 

 

This seems to have started happening after I changed my default nic in unraid.

 

Here are my logs

 

<log removed>

 

Could you edit the container and change/add the following:

Change the "Repository" field to "dyonr/jackettvpn:dev"

 

 

Add another Path, Port, Variable, Label or Device

> Config Type: Variable

> Name: RESTART_CONTAINER

> Key: RESTART_CONTAINER

> Value: 0

> Default Value: 0

> Description: (empty)

> Display: Always

> Required: No

> Password Mask: no

 

This will add a new variable called RESTART_CONTAINER, if this is set to '1', 'yes' or 'true', it will exit the container when the network is down. When set to something else (like 0) it won't shut down.  

 

After changing this, start the container, open the console and please check if you can run the command `ping one.one.one.one`.

 

Edited by Dyon
  • Upvote 1
Link to comment
12 minutes ago, Dyon said:

 

Could you edit the container and change/add the following:

Change the "Repository" field to "dyonr/jackettvpn:dev"

 

 

Add another Path, Port, Variable, Label or Device

> Config Type: Variable

> Name: RESTART_CONTAINER

> Key: RESTART_CONTAINER

> Value: 0

> Default Value: 0

> Description: (empty)

> Display: Always

> Required: No

> Password Mask: no

 

This will add a new variable called RESTART_CONTAINER, if this is set to '1', 'yes' or 'true', it will exit the container when the network is down. When set to something else (like 0) it won't shut down.  

 

After changing this, start the container, open the console and please check if you can run the command `ping one.one.one.one`.

 

After adding the new variable, I can get into the console, I am unable to ping one.one.one.one, or any other domain names. I am able to ping IP addresses.

 

I can get to the webui now also.

 

 

Link to comment
38 minutes ago, xcsascii said:

After adding the new variable, I can get into the console, I am unable to ping one.one.one.one, or any other domain names. I am able to ping IP addresses.

 

I can get to the webui now also.

 

 

 

Alright, then it seems to be something related to the DNS.

Could you run "cat /etc/resolv.conf" in the terminal and share the output

  • Thanks 1
Link to comment
4 minutes ago, Dyon said:

 

Alright, then it seems to be something related to the DNS.

Could you run "cat /etc/resolv.conf" in the terminal and share the output

nameserver 10.10.10.30
nameserver 10.10.10.31
nameserver 10.10.10.1
nameserver 1.1.1.1
nameserver 1.0.0.1

 

The first 3 are my local DNS servers. I am assuming I need to remove them? I am not really sure how. 

Link to comment
5 minutes ago, xcsascii said:

nameserver 10.10.10.30
nameserver 10.10.10.31
nameserver 10.10.10.1
nameserver 1.1.1.1
nameserver 1.0.0.1

 

The first 3 are my local DNS servers. I am assuming I need to remove them? I am not really sure how. 

 

It is normal that your local DNS is listed in there, so no need to change that.

You are running it in Bridge mode, which is correct, which I can see from the log

Looking extensively at your log, I don't see anything different compared to mine.

 

Kinda out of ideas, only I could suggest now is to restart your Unraid and check your Docker and Network settings.

 

In Unraid, can you check if Settings -> Docker (show advanced view) -> IPv4/6 custom network info makes sense.

For comparison mine:

IPv4 custom network on interface br0:

Subnet: 192.168.0.0/24

Gateway: 192.168.0.1

 

IPv6 custom network on interface br0:

Subnet: 2001::a300::/64

Gateway: fe80::eaa5

 

For all DHCP pool: not set

 

And also, check you Settings -> Network Settings

 

Here is my routing table for comparison:

image.thumb.png.c197b6304a7c19a697a4fa6ef383e9f6.png

 

 

  • Like 1
Link to comment

Thanks for the help so far. 

 

My routing table looks slightly different as I have shim-br0 due to enabling: allow access to host networks

 

I noticed that if I change my network type to Custom : br0, and connect to the console I can ping one.one.one.one, but I cannot access the webui. 

 

I am also using PIA if that makes any difference.

 

routing table-unraid.png

Link to comment

Good evening all, I am currently experiencing the same issue as @xcsascii. Been running strong for over a year and the most recent update I performed on the the container seems to have broken it. Starting to work through the troubleshooting steps now.

 

Edit: After changing the repo to 'dyonr/jackettvpn:dev' and creating the RESTART_CONTAINER variable, the issue is even worse. The port mapping doesn't complete and I can't access the WebUI or logs to view what's going on with the container.

Edited by Skyshroud
Link to comment
10 minutes ago, Skyshroud said:

Good evening all, I am currently experiencing the same issue as @xcsascii. Been running strong for over a year and the most recent update I performed on the the container seems to have broken it. Starting to work through the troubleshooting steps now.

 

Edit: After changing the repo to 'dyonr/jackettvpn:dev' and creating the RESTART_CONTAINER variable, the issue is even worse. The port mapping doesn't complete and I can't access the WebUI or logs to view what's going on with the container.

On your edit, if you power down the container, then look at logs they wont just close. 

  • Like 1
Link to comment

Very odd. Nothing has changed to the container since February. Iy only auto-updates / rebuilds whenever a new Jackett version has been released (which fixes indexing trackers). Nevertheless, I will investigate and look into what could be wrong.

 

Which Unraid version are you running @Skyshroud and @xcsascii?

Edited by Dyon
  • Like 1
Link to comment
10 hours ago, Dyon said:

Very odd. Nothing has changed to the container since February. Iy only auto-updates / rebuilds whenever a new Jackett version has been released (which fixes indexing trackers). Nevertheless, I will investigate and look into what could be wrong.

 

Which Unraid version are you running @Skyshroud and @xcsascii?

I am on Version: 6.11.1

 

One other thing I wanted to mention is that when I add the RESTART_CONTAINER variable, the logs show:

[ERROR] Network is possibly down.
[INFO] Network is up
 

Over and over again, I am assuming this is the health check. 

 

Link to comment

Ok, I think I may have figured out my issue. I was looking at another vpn container I am running, and found that it did not have any of my local DNS servers in resolv.conf.

 

I modified resolv.conf on the jackettvpn container and removed my local DNS servers. Only keeping 1.1.1.1 and 1.0.0.1. 

 

I am now able to use jackettvpn without any issues.

 

Thanks for helping me better understand containers @Dyon learned a lot!

 

EDIT: Just to give you some background on my configuration incase this helps someone else in the future.

 

I am running 2x PiHole, and using PIA for VPN. I was able to ping local DNS, but was unable to resolve any domain names. I am unsure if using local based DNS caused the issue, or if it was something specific to PiHole that was causing my issue. 

Edited by xcsascii
Link to comment
  • 4 months later...

Aloha all, I'm hoping for some input that could help resolved my issue here

 

I've been using this jacketvpn container for over a year now and now can't access the webgui. The logs show the server is up and there's no issue. Here's a quick list of the things I've tried/checked

  • I can ping IPs and DNS entries from within the container
  • Reboot the container didn't help
  • Restarting the docker service did not help
  • Rebooting the entire server did not help
  • Installing a fresh jackettvpn with a new config directory did not help
  • Changing the docker network from ipvlan to macvlan back to ipvlan did not help (I usually access my server through a wireguard vpn, so many efforts were focused on that
  • I created a windows vm to see if I could connect to the docker within my home network, this did not work.
  • I changed the docker tags to both dev and buster, but this did not help
  • I've tried a few different PIA openvpn files, to no avail
     

After everything so far, I'm inclined to believe there's something wrong with the docker itself and not my configuration, hence this post, to sanity check against anyone else using this docker and possibly get some help!

 

I'm running Unraid 6.11.5.

 

Logs below (The vpn is off for testing, but no webgui when its enabled:)

Quote

2023-03-06 09:05:46.991003 [INFO] VPN_ENABLED defined as 'no'
2023-03-06 09:05:47.059563 [INFO] The container is currently running iptables v1.8.2 (nf_tables).
2023-03-06 09:05:47.097911 [INFO] LEGACY_IPTABLES is set to ''
2023-03-06 09:05:47.134126 [INFO] Not making any changes to iptables version
2023-03-06 09:05:47.173753 [WARNING] !!IMPORTANT!! You have set the VPN to disabled, your connection will NOT be secure!
2023-03-06 09:05:47.225832 [INFO] Adding 1.1.1.1 to resolv.conf
2023-03-06 09:05:47.266162 [INFO] Adding 1.0.0.1 to resolv.conf
2023-03-06 09:05:47.550309 [INFO] A group with PGID 100 already exists in /etc/group, nothing to do.
2023-03-06 09:05:47.588351 [INFO] An user with PUID 99 already exists in /etc/passwd, nothing to do.
2023-03-06 09:05:47.624838 [INFO] UMASK defined as '002'
2023-03-06 09:05:47.739879 [INFO] Starting Jackett daemon...
Logging to /config/Jackett/Logs/log.txt.
2023-03-06 09:05:48.827348 [INFO] Started Jackett daemon successfully...
2023-03-06 09:05:49.089055 [INFO] Jackett PID: 68
2023-03-06 09:05:49.187622 [INFO] Network is up
2023-03-06 09:10:49.277561 [INFO] Network is up
2023-03-06 09:15:49.347507 [INFO] Network is up
2023-03-06 09:20:49.409466 [INFO] Network is up

 

 

Edited by naturalcarr
Adding information
Link to comment
  • 3 months later...

Hello,

I'm triying to set JackettVPN, I'm using wireguard config file from Windscribe. If I set :


 

VPN_ENABLED = Yes
VPN_TYPE = wireguard

 

Container starts, but log window closes itself and I can't access to the webui. If I disable the VPN env, everything works.

 

Log :

 

2023-06-14 21:12:55.737948 [INFO] VPN_ENABLED defined as 'yes'
2023-06-14 21:12:55.754927 [INFO] The container is currently running iptables v1.8.7 (nf_tables).
2023-06-14 21:12:55.770428 [INFO] LEGACY_IPTABLES is set to ''
2023-06-14 21:12:55.786107 [INFO] Not making any changes to iptables version
2023-06-14 21:12:55.801926 [INFO] VPN_TYPE defined as 'wireguard'
2023-06-14 21:12:55.821946 [INFO] WireGuard config file is found at /config/wireguard/wg0.conf
dos2unix: converting file /config/wireguard/wg0.conf to Unix format...
2023-06-14 21:12:55.841793 [INFO] VPN remote line defined as 'censured.windscribe.com:1194'
2023-06-14 21:12:55.858427 [INFO] VPN_REMOTE defined as 'censured.windscribe.com'
2023-06-14 21:12:55.875519 [INFO] VPN_PORT defined as '1194'
2023-06-14 21:12:55.890937 [INFO] VPN_PROTOCOL set as 'udp', since WireGuard is always udp.
2023-06-14 21:12:55.906661 [INFO] VPN_DEVICE_TYPE set as 'wg0', since WireGuard will always be wg0.
2023-06-14 21:12:55.923476 [INFO] LAN_NETWORK defined as '192.168.1.0/24'
2023-06-14 21:12:55.940121 [INFO] NAME_SERVERS defined as '9.9.9.9,149.112.112.112'
2023-06-14 21:12:55.957011 [INFO] Adding 9.9.9.9 to resolv.conf
2023-06-14 21:12:55.973795 [INFO] Adding 149.112.112.112 to resolv.conf
2023-06-14 21:12:55.989324 [INFO] Starting WireGuard...
Warning: `/config/wireguard/wg0.conf' is world accessible
[#] ip link add wg0 type wireguard
[#] wg setconf wg0 /dev/fd/63
[#] ip -4 address add censured/32 dev wg0
[#] ip link set mtu 1420 up dev wg0
[#] resolvconf -a wg0 -m 0 -x
[#] wg set wg0 fwmark 51820
[#] ip -6 route add ::/0 dev wg0 table 51820
Error: IPv6 is disabled on nexthop device.
[#] resolvconf -d wg0 -f
[#] ip link delete dev wg0

 

Edited by Alex.b
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.