h0tw1r3/aria2.daemon

it's worked !
)

more to aria2.daemon:

##files
dir=/user/downloads
file-allocation=falloc
continue=true
daemon=true
disk-cache=32M

##logging
log=/user/aria2/aria2.log
console-log-level=warn
log-level=notice

##downloads
max-concurrent-downloads=5
max-connection-per-server=5
min-split-size=20M
split=4
disable-ipv6=true

##sessions
force-save=true
input-file=/user/aria2/ses/aria2.session
save-session=/user/aria2/ses/aria2.session
save-session-interval=10

##security
http-auth-challenge=true
check-certificate=false
enable-rpc=true
rpc-listen-all=true
rpc-secret=*YOUR TOKEN*

#rpc-secure=true	
#rpc-allow-origin-all=true
#rpc-certificate=/user/aria2/cet/aria2.pfx

##ports
rpc-listen-port=6800

##others
summary-interval=120
enable-dht=true

##times
timeout=600
retry-wait=30
max-tries=50
```

Thanks guys.

I couldn't set User=www-data. It wouldn't work with this user, and if I omitted the setting, then all the saved files were owned by root. So I changed this to User={myusername}. There's also no need to run the arguments after the aria2c binary since the daemon can pass those same arguments anyhow (i.e., --console-log-level=warn --enable-rpc --rpc-listen-all). Lastly, the documentation states that file-allocation=falloc is best for newer file systems, e.g., ext4. I think that's what most Linux users have, especially newbies.

Added to config:

• rpc-secret (example, you should change!)
• rpc-allow-origin-all (easy for new users to use a web front-end like AriaNg)
• input-file and save-session to auto resume downloads on service start
• changed file-allocation to falloc for performance

Added to unit:

• ensure session file exists otherwise aria2c will fail to start
• add Group, note User and Group should be changed per your local environment
• added restart on failure
• added stop timeout

where do I put the .daemon file as user?
I know .service goes to ~/.config/systemd/user/

@tazihad if you're going to use it as a user service, change --conf-path in ExecStart to the path where aria2.daemon will be.

@tazihad if you're going to use it as a user service, change --conf-path in ExecStart to the path where aria2.daemon will be.

Systemd User Service cannot contain neither User= or Group= line,
otherwise it could result error like
"aria2.service: Failed to determine supplementary groups: Operation not permitted"

I just google this bug for hours, before realizing that user service cannot use any group (even user itselves' group).