I only configured the port 5800:5800 and it worked.
Wow. Great! Thanks!
But I believe what we are seeing is just this filezilla container environment. But with a shared folde this could come in handy for remote backups.
Has anyone been able to use the container eclipse-mosquitto ?
I know that the port 1883 is not allowed as said here:
I started the container as Bridge with ports 50122:1884 as showed by @Alexie :
Created the on /config/mosquitto.conf with lines “allow_aonymous true” and “listener 1884” using the filebrowser:
But it can’t use another port, even with file mosquitto.conf, the mosquitto starts with port 1883:
I also tried initing the container as Host with /config/mosquitto.conf and the behavior was the same.
Do you know where this configuration data is stored? I have a new add-on to install and I want to configure it in the filebrowser. Do you know if I have to delete the old one and create a new filebrowser instance every time I want to modify some configuration?
Yes, you need to remove the instance from the details page, see in the pic, and run it again, the files won’t be affected.
Thanks for the prompt response. Is there any chance that in the future it will be possible to use some kind of configuration file for add-ons, like Docker Compose? It would be extremely useful.
We’re working on Docker Compose, and if things go well we might see it in December. If there are some difficulties that need to be resolved, it may not be released until next year
3 Likes
If I already have Filebroswer and NodeRED running is it possible to adjust the volumes I can see in Filebrowser or do I have to start new remembering to select the correct file this time?
If I need to delete and restart Filebrowser how do I add an existing NodeRED docker?
I’ve been trying to figure out if this is possible but the impression I have is that I need to start again with FileBrowser and then figure out where NodeRED is - is that correct?
Please download your system log and post it here.
We’ll see what’s wrong.
I cannot find a way to add an additional add-on volume after I installed and run filebrowser.
As far as I could see, there is no way to add something after it has already been created.
We always have to delete it and recreate it with the new parameter.
Containers are meant to be disposable. That’s a core rule using Docker.
1 Like
I think the problem is that you can’t map new volumes to filebrowser after it’s already running.
I currently have about 10 volumes mapped to filebrowser.
If I need to map one more then I have to stop filebrowser and recreate it adding all 10 mappings plus the additional one.
Hi!
Can you explain how “For filebrowser I mapped this volume with /srv/homeassistant”?
I can create folder in File Browser but its always remain empty after install Node Red.
- I created a volume called NodeRed-Files
- created a folder in File Browser with the same name: NodeRed-Files
- Node Red installed and the “NodeRed-Files” folder name given.
- I see in Volumes that NodeRed-Files is in use, but the NodeRed-Files folder in File Browser still empty.
I tried 10 times nothing.
Regards
Peter
You mean you select it from the drop down list here?
On the RH side I have found it better to put
/srv/dataThen run Node-Red addon and on the RH side enter
/dataI have done this several times and have found that when it comes to writing files in Node-Red, to the context folder, after enabling context memory, /data/context/ will be understood, otherwise it seems to default to the working directory of the Node-RED process and cannot be seen.
Thanks!! Problem solved!!
I deleted File Browser, Node Red and HomeAssistant and reinstalled all according to your instructions.
Lesson: You are able to see in File Browser only those folders what you created during the installation of File Browser.
Thanks for your help.
BR
Peter