Jump to content

VieuxCrabe

Members
  • Posts

    4
  • Joined

  • Last visited

Posts posted by VieuxCrabe

  1. Well... Plex seems to have fixed itself with one more Update button click  :o

     

    Transmission is still out of service...

     

     

    *update*

     

    I uninstalled transmission, rebooted, manually deleted the folder named 'transmission' on the cache drive (config, etc), rebooted and installed again.

     

    It works  :o

     

    Lesson learned, I'm done updating for a while...

     

  2. Hi guys,

     

    Hopefully someone can point me in the right direction.

     

    I was running Transmission with no problem whatsoever, and suddenly it showed an update available on the settings page.

    Update was version 2.84, which I'm pretty sure I already had, but clicked anyway.

     

    The update completed but Transmission failed to start. And it is still showing the update button for version 2.84...

     

    I clicked on Start: "Starting Transmission... PID not created, application did not start for some reason"

     

    Completely uninstalled plugin, rebooted and reinstalled. Same problem.

     

    My log shows:

     

    Jun 4 00:42:59 Myserver sudo: root : TTY=unknown ; PWD=/usr/local/emhttp ; USER=nobody ; COMMAND=/bin/bash -c . /usr/local/PhAzE-Common/Transmission/startcfg.sh; /mnt/cache/apps/Transmission/usr/bin/transmission-daemon --version 2>&1

    Jun 4 00:43:00 Myserver sudo: root : TTY=unknown ; PWD=/usr/local/emhttp ; USER=nobody ; COMMAND=/bin/bash -c . /usr/local/PhAzE-Common/Transmission/startcfg.sh; curl --version 2>&1

    Jun 4 00:43:09 Myserver emhttp: /etc/rc.d/rc.Transmission buttonstart 2>&1

    Jun 4 00:43:10 Myserver sudo: root : TTY=unknown ; PWD=/ ; USER=nobody ; COMMAND=/bin/bash -c . /usr/local/PhAzE-Common/Transmission/startcfg.sh; nohup /mnt/cache/apps/Transmission/usr/bin/transmission-daemon -p 9091 -g /mnt/cache/apps/Transmission/config -T --logfile /mnt/cache/apps/Transmission/config/logs/Transmission.log -x /var/run/Transmission/Transmission.pid > /dev/null 2>&1 &

    Jun 4 00:43:26 Myserver emhttp: sendOutput: write

    Jun 4 00:43:26 Myserver emhttp: sendOutput: write

    Jun 4 00:43:27 Myserver sudo: root : TTY=unknown ; PWD=/usr/local/emhttp ; USER=nobody ; COMMAND=/bin/bash -c . /usr/local/PhAzE-Common/Transmission/startcfg.sh; /mnt/cache/apps/Transmission/usr/bin/transmission-daemon --version 2>&1

    Jun 4 00:43:28 Myserver sudo: root : TTY=unknown ; PWD=/usr/local/emhttp ; USER=nobody ; COMMAND=/bin/bash -c . /usr/local/PhAzE-Common/Transmission/startcfg.sh; curl --version 2>&1

    Jun 4 00:45:46 Myserver emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1

     

     

    Any hint on how to fix this?

     

    Thanks!

     

    *edit* : I have the same problem with Plex as you can see on the attached jpg

    plex.jpg.199e521db312b521de911545c2334036.jpg

  3. Hey Phaze, any chance you will be updating PlexConnect to make it use the iMove or Wall Street Journal App?  No hurry just wondering if you are going to look at it and when it might happen.

     

    Thanks for the great work

    I will have a look likely later this week. Can you tell me what needs to be done, like is it just the. Pem name that needs updating? Right now it forces trailers.pem

     

    Hi,

     

    Don't know if this was answered or not.

     

    Basically, it would be perfect if the plugin DID NOT force trailers.pem

    Once the app and certificate are set, there is no need to force anything on each upgrade.

     

    My settings.cfg is set like this:

     

    hosttointercept = secure.marketwatch.com

    certfile = /mnt/cache/apps/Plexconnect/config/certificates/wsjapp.pem

     

    But on each upgrade it ends up like this:

     

    hosttointercept = secure.marketwatch.com

    certfile = /mnt/cache/apps/Plexconnect/config/certificates/trailers.pem

     

    So I need to stop Plexconnect, edit the setting and restart Plexconnect after a plugin update.

    No biggie, but it would be nice it it didn't force the certificate name  ;)

     

    Thanks for all the work!

     

  4. Anyone having a problem with the hijacked app certificate set in settings.cfg reverting to trailers after an update?

     

    I have Settings.cfg set to use secure.marketwatch.com and wsjapp.pem

    When I upgrade, secure.marketwatch.com sticks but wsjapp.pem is changed for trailers.pem

     

    I made sure Plexconnect was stopped when editing the file but it still reverts to the default app.

     

    Here is my Settings.cfg file:

     

    [PlexConnect]

    enable_plexgdm = True

    ip_pms = 0.0.0.0

    port_pms = 32400

    enable_dnsserver = True

    port_dnsserver = 53

    ip_dnsmaster = 8.8.8.8

    prevent_atv_update = True

    enable_plexconnect_autodetect = True

    ip_plexconnect = 0.0.0.0

    hosttointercept = secure.marketwatch.com

    port_webserver = 80

    enable_webserver_ssl = True

    port_ssl = 443

    certfile = /mnt/cache/apps/Plexconnect/config/certificates/wsjapp.pem

    allow_gzip_atv = False

    allow_gzip_pmslocal = False

    allow_gzip_pmsremote = True

    loglevel = Normal

    logpath = /mnt/cache/apps/Plexconnect/config/logs

     

    Thanks to all!

×
×
  • Create New...