Access Web-GUI on headless Raspberry Pi

I have installed Openmediavault on a headless Raspberry Pi. I have installed Rclone with ...

curl https://rclone.org/install.sh | sudo bash

... and I want to access the web-gui from another machine on the network using ...

192.168.1.198:5572

... so I run ...

rclone rcd --rc-web-gui-no-open-browser --rc-addr 192.168.1.198:5572

... (I am logged in as root) and I get the message ...

Serving remote control on http://192.168.1.198:5572/

... but all I get in my browser is 'Not found'.

What am I doing wrong?

Check out

https://rclone.org/gui/

So, I've added --rc-serve flag and now I get access to something but it seems to be a stripped down version of the web-gui.

If I run ...

rclone rcd --rc-web-gui --rc-addr 192.168.1.198:5572

... and then manually browse to the address that it generates then I can access it fine :slight_smile:

However, how can I access it without having to run this command on the nas every time I want to access the gui?

I'm not sure how you autostart on your NAS, but you'd add --daemon to let it run in the background.

Thanks but not sure how to add --daemon flag as it's not recognised as rclone flag.

Situation ...

  • Openmediavault NAS running on Raspberry Pi at LAN address 192.168.1.198 (dhcp assigned so may change)
  • I've installed rclone on the NAS through curl and added a remote through the cli for Google Drive using Putty from my laptop and manually authenticating.
  • Added a scheduled reboot task in omv with the following command ...

rclone rcd --rc-web-gui-no-open-browser --rc-user rclone --rc-pass password --rc-addr 192.168.1.198:5572 --rc-serve

Workflow ...

  1. Start rclone gui in the background on openmediavault reboot so I can access rclone config through the browser.
  2. Use scheduled tasks in openmediavault to run rclone at specific times to backup the NAS to cloud and transfer files from certain folders on the nas to the cloud.

Behaviour ...

  • The rclone GUI does not restart at reboot. I have to start it manually.
  • When I access 192.168.1.198:5572 I get a slimmed down version of the web-gui with just a file browser for the remote and no left panel and the title 'list of all clone remotes'
  • If I change the cron command to ... rclone rcd --rc-web-gui --rc-user rclone --rc-pass password --rc-addr 192.168.1.198:5572 --rc-serve ... and rerun the command, I get errors about not being able to open the browser (which is fine because it's headless) but then when I browse to 192.168.1.198:5572 I get the full GUI.
  • Now if I try to create a new remote, I get strange behaviour. When I click 'Create', a message appears telling me that a new browser will open to allow me to authenticate and then lots of network errors. I then get errors in openmediavault ...

Remote config Use auto config? * Say Y if not sure * Say N if you are working on a remote or headless machine Auto confirm is set: answering Yes, override by setting config parameter config_is_local=false If your browser doesn't open automatically go to the following link: http://127.0.0.1:53682/auth?state=fGCl_xV6QNdmsgBsPeo8pw Log in and authorize rclone for access Waiting for code... Remote config Use auto config? * Say Y if not sure * Say N if you are working on a remote or headless machine Auto confirm is set: answering Yes, override by setting config parameter config_is_local=false 2020/06/14 11:46:36 Failed to configure token: failed to start auth webserver: listen tcp 127.0.0.1:53682: bind: address already in use

I don't know whether this make sense or whether I'm trying to do something which can't be done. Thanks for your help.

Oh, that's right as --daemon is for mounts. My bad!

Sorry as I don't use a NAS so I am not sure how you'd autostart. On Linux, we'd use systemd..

You probably want to pick headless since you aren't on a GUI on that system I would think.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.