Lebowski

Members
  • Posts

    202
  • Joined

  • Last visited

Posts posted by Lebowski

  1. @spants

     

    Sure, here is the config: If I need to change it to false that's fine. I wasn't even sure if its an issue as everything is functioning just fine.

     

     

    # Place your local configuration in /config/conf.d/
    
    retry_interval 20
    sys_interval 10
    store_clean_interval 10
    max_inflight_messages 40
    max_queued_messages 200
    queue_qos0_messages false
    message_size_limit 0
    allow_zero_length_clientid true
    persistent_client_expiration 3m
    allow_duplicate_messages false
    autosave_interval 60
    autosave_on_changes false
    allow_anonymous false
    
    persistence true
    persistence_file mosquitto.db
    persistence_location /config/data/
    
    user mosquitto
    
    # Port to use for the default listener.
    listener 1883
    
    listener 9001
    protocol websockets
    
    log_dest stderr
    log_type all
    connection_messages true
    log_timestamp true
    
    include_dir /config/conf.d
    
    # If the password.mqtt file is empty, this has no effect.
    allow_anonymous true
    
    # DO NOT CHANGE THIS LINE BELOW!!!
    password_file /config/passwords.mqtt

     

  2. On 9/30/2019 at 11:00 PM, tuxflux said:

    I'm having problems making a setting for a plugin stick. I use the Extractor plugin to unpack RAR's downloaded by Radarr and Sonarr and they both look for the extracted file in the original folder for the Torrent in question. The plugin has an option to create a sub-folder with the name of the torrent, which basically defaults to the torrent being extracted to the same folder and the rest of the automated process to complete successfully.

     

    However, this gets reset every time the container is restarted or updated. My server updates dockers automatically once a week, and I don't always remember to reactivate this option. I've tried several different plugins with the same result, hence I assume that this is a problem with the Unraid docker and not the plugin itself, and that's why I'm asking in this thread. Any ideas?

     

    image.png.e8bcd5248d3f22fe211f2627dd299c95.png

    I am having troubles getting 3rd party plugins to stick, I can get WebAPI plugin working but as soon as the deluge docker is restarted the settings are lost and I need to manually add it back. The only way to add it back is to delete webapi.conf file and re-enable to plugin. Its lost again on restart.

     

    Manually edit of the config files has the same issues.

  3. Been running my second unRaid machine for months without any hiccups, found that it had locked up with the following error on the screen

     

    Any suggestions to what this could be? I was not able to ping it or anything like that. Its reset and working okay again.

    Error.png

  4. anyone have this going with Home Assistant? I have it working fine, but on some occasions I have to hit the "retry" button to login. After clicking retry its fine. It can cause the IOS app to be blocked for a short period but it also comes good if you force close the app and re-open.

     

    I figure I might need to add extra settings for 100% compatibility?

  5. how did you have your media stored? Emby needs each movie in its own folder from my experience. If for example you have all your MKV’s in one directory and you delete a movie via the emby menu it will delete the parent directory including the rest of the mkv’s in that folder. I found that out the hard way 2 years ago. Lucky I had back ups on my second server.

  6. On 2/2/2019 at 1:20 PM, aptalca said:

    For anyone who's having issues with openvpn on unraid 6.7 rc, switch it to run in bridge networking, remove the INTERFACE variable setting or set it to eth0 (default) and map the ports 943 and 9443 for tcp and 1194 for udp

    I should have clicked back a few pages. Working fine now. Thank you 

  7. 10 hours ago, [email protected] said:

    Hi All, 

     

    I've been getting the following error:

     

    service failed to start due to unresolved dependencies: set(['user'])

    service failed to start due to unresolved dependencies: set(['iptables_openvpn'])

    Service deferred error: IPTablesServiceBase: failed to run iptables-restore [status=2]: ['iptables-restore v1.6.0: Bad IP address ""', '', 'Error occurred at line: 151', "Try `iptables-restore -h' or 'iptables-restore --help' for more information."]: internet/defer:323,sagent/ipts:122,sagent/ipts:49,util/mycprof:11,<string>:1,sagent/sagent_entry:14,sagent/sagent_entry:11,util/daemon:28,util/daemon:69,application/app:423,scripts/_twistd_unix:202,application/app:445,application/app:348,internet/base:1166,internet/base:1178,internet/epollreactor:194,python/log:85,python/log:70,python/context:59,python/context:37,internet/epollreactor:223,internet/posixbase:191,internet/process:260,internet/process:762,internet/process:775,internet/_baseprocess:60,svc/pp:117,svc/svcnotify:32,internet/defer:238,internet/defer:307,internet/defer:323,sagent/ipts:122,sagent/ipts:49,util/error:61,util/error:44

    service failed to start due to unresolved dependencies: set(['user', 'iptables_live', 'iptables_openvpn'])

    service failed to start due to unresolved dependencies: set(['iptables_live', 'iptables_openvpn']). 

     

    This occurs every time I try to start the server, however, the container starts without a hitch.

     

    I've tried to restore the container, delete the config files, install a different version, ect. Not sure what to do at this point.

    I'm also new to OPENVPN and linux so please be specific if you have any suggestions.

     

    Thanks!

    Same problem here, been working fine for months, I have the same issue.

  8. On 1/14/2019 at 8:57 PM, Djoss said:

    Yes this is a known issue.  Note that as a workaround, you can change this setting from the console at crashplan.com/console

    Is this something being worked on?

     

    I have been really frustrated with Crashplan, the upload speed has turned to sh*t here is Australia. Its crawling to the point of not being usable. 

     

    May have to look at something else.

  9. On 11/29/2018 at 7:34 AM, Zoc said:

    There we have it!

     

    There was somehow a space introduced in the beginning of the token when the container was installed.

    This then apparently followed me around when i reinstalled.

     

    Sometimes the simple things..

     

    Thanks @aptalca!

    If you copy and paste the token from duckdns it has a space in front of it. 

    • Upvote 1