Skip to content
This repository has been archived by the owner on Aug 22, 2022. It is now read-only.

iodine bug #123

Open
attuska opened this issue Feb 12, 2022 · 0 comments
Open

iodine bug #123

attuska opened this issue Feb 12, 2022 · 0 comments

Comments

@attuska
Copy link
Contributor

attuska commented Feb 12, 2022

`● iodined.service
Loaded: loaded (/usr/lib/systemd/system/iodined.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2022-02-12 11:52:12 CET; 14min ago
Process: 29756 ExecStart=/usr/sbin/iodined -f -c -l $IODINE_BIND_ADDRESS -n $IODINE_EXT_IP -p $IODINE_PORT -P $IODINE_PASSWORD -u $IODINE_USER $TUN_IP $TOP_DOMAIN (code=exited, status=2)
Main PID: 29756 (code=exited, status=2)
CPU: 2ms

febr 12 11:52:12 attila-pc systemd[1]: Started iodined.service.
febr 12 11:52:12 attila-pc iodined[29756]: Usage: iodined [-v] [-h] [-c] [-s] [-f] [-D] [-u user] [-t chrootdir] [-d device] [-m mtu] [-z context] [-l ip address to listen on] [-p port] [-n external ip] [-b dnsport] [-P password] [-F pidfile] [-i max idle time] tunnel_ip[/netmask] topdomain
febr 12 11:52:12 attila-pc systemd[1]: iodined.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
`

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

1 participant