Kodi Community Forum

Full Version: [WIP] HTPC-Manager Beta, Manage XBMC, Sabnzbd, SickBeard with one app
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
(2015-05-23, 15:08)reaven Wrote: [ -> ]really great application, love it ! Nod
Being a very visual person, is there any word on themes/templates developing, since I saw a Style section with theme and template support ? it would be great to develop themes and change the looks a little since it already do a great job pulling and displaying info from our favorite apps.

Great work !

I'm not really sure what you talking about. Buts its possible to make themes.

See this pr for how to add it to htpc-manager: https://github.com/Hellowlol/HTPC-Manage...6f21f73a21

Use this to modify bootstrap: http://pikock.github.io/bootstrap-magic/2.3.2/
(2015-05-23, 15:19)hellow Wrote: [ -> ]
(2015-05-23, 15:08)reaven Wrote: [ -> ]really great application, love it ! Nod
Being a very visual person, is there any word on themes/templates developing, since I saw a Style section with theme and template support ? it would be great to develop themes and change the looks a little since it already do a great job pulling and displaying info from our favorite apps.

Great work !

I'm not really sure what you talking about. Buts its possible to make themes.

See this pr for how to add it to htpc-manager: https://github.com/Hellowlol/HTPC-Manage...6f21f73a21

Use this to modify bootstrap: http://pikock.github.io/bootstrap-magic/2.3.2/

I was talking about this
Image

but thanks for the links
I believe I answered the question the .

The template does nothing as its only one and all the HTML text are there, if you add template support you have to restructure the project.

There is no way to change look and feel except from within htpc manager gui except for themes.

Each theme has a folder and inside them you have a bootstrap css file and style.css. Style.css is used to override any default bootstrap behavior.
(2015-05-23, 15:08)reaven Wrote: [ -> ]really great application, love it ! Nod
Being a very visual person, is there any word on themes/templates developing, since I saw a Style section with theme and template support ? it would be great to develop themes and change the looks a little since it already do a great job pulling and displaying info from our favorite apps.

Great work !

Not really. Only TwitterBootstrap themes are supported. You could create your own and store the css in interfaces/default/css/themes.
(2015-05-25, 15:05)styxit Wrote: [ -> ]
(2015-05-23, 15:08)reaven Wrote: [ -> ]really great application, love it ! Nod
Being a very visual person, is there any word on themes/templates developing, since I saw a Style section with theme and template support ? it would be great to develop themes and change the looks a little since it already do a great job pulling and displaying info from our favorite apps.

Great work !

Not really. Only TwitterBootstrap themes are supported. You could create your own and store the css in interfaces/default/css/themes.

great I will look into that, thanks to both of you!
I'm running CentOS 6 with the latest version of Sickbeard and HTPC. However, while I was able to get other things to work -e.g. SABnzbd I'm not able to get Sickbeard to work properly with HTPC Manager.

I looked in the htpcmanager.log but don't see anything failing with the tests.

Anyone have any suggestions with Sickbeard and HTPC Manager?
(2015-06-05, 04:24)htpcuser2 Wrote: [ -> ]I'm running CentOS 6 with the latest version of Sickbeard and HTPC. However, while I was able to get other things to work -e.g. SABnzbd I'm not able to get Sickbeard to work properly with HTPC Manager.

I looked in the htpcmanager.log but don't see anything failing with the tests.

Anyone have any suggestions with Sickbeard and HTPC Manager?

You need to help us to help you Smile

Shutdown htpc manager and start it again with Htpc.py --loglevel debug,
- Delete the log.
- Check your settings (placeholders can look like values)
- Press the sickbeard test button.
- Enter the module, see any errors?

upload the full log to pastebin and post a link to it here.
(2015-06-05, 04:24)htpcuser2 Wrote: [ -> ]I'm running CentOS 6 with the latest version of Sickbeard and HTPC. However, while I was able to get other things to work -e.g. SABnzbd I'm not able to get Sickbeard to work properly with HTPC Manager.

I looked in the htpcmanager.log but don't see anything failing with the tests.

Anyone have any suggestions with Sickbeard and HTPC Manager?

I also couldn't get SickBeard to work upon testing connection from HTPC manager. Did you get this error in your SB log? --> WARNING CP Server Thread-7 :: API :: 127.0.0.1 - SB API Disabled. ACCESS DENIED
I got that error even though API in SickBeard was enabled.

Sollution: Restart SickBeard Tongue (using Synology NAS)
Is it possible to use all the modules without specifying a port? I have all my servers running behind a reverse proxy so the ports aren't forwarded.

When I click on the nzbget tab it will try to go to http://mydomain.us:/nzbget instead of the actual location of http://mydomain.us/nzbget
(2015-06-08, 18:45)brando56894 Wrote: [ -> ]Is it possible to use all the modules without specifying a port? I have all my servers running behind a reverse proxy so the ports aren't forwarded.

When I click on the nzbget tab it will try to go to http://mydomain.us:/nzbget instead of the actual location of http://mydomain.us/nzbget

No it's not, fixing this would be a problem as htpc manager goes a long way to attempt to fix user errors.

Are htpc manager not running on the same network as the other services?

The general idea is to use the ports as its intended. If you expose htpc-manager to the web on mydomain.com the URL to nzbget tab is my domain.com/nzbget.

Isn't this what you want?
HTPC Manager and all my other usenet apps (including my apache server) are running in the same jail.

Here's a section from my apache24/extras/httpd-vhost.conf
Code:
<location /nzbget>
  ProxyPreserveHost On
  ProxyPass http://192.168.1.100:6789/nzbget
  ProxyPassReverse http://192.168.1.100:6789/nzbget
</location>

If I enter mydomain.com, no port, and the webdir of /nzbget into the nzbget section of the HTPC Manager config page, the RPC calls from within HTPC manager don't work (no latest downloads, no history, etc...) because it's trying to contact http://mydomain.com:/nzbget (notice the colon after com) and that shows up in my logs, although if I click on the NZBget tab at the top of the page it proxies me to the actual NZBget page instead of the NZBget page within HTPC Manager.

If I use the local IP and port number of nzbget in the HTPC manager config, the RPC calls still don't work, and if I click the NZBget tab it still brings me directly to NZBget and not the NZBget page within HTPC Manager.

If I change the location directive from /nzbget to /nzbget1 the RPC calls now work. The problem arises when I click on the NZBget link at the top of the NZBget page, because the external website that it tries to connect to is http://192.168.1.100:6789 which obviously won't work outside of my network.

How can I make it so that the RPC calls still work within HTPC Manager and when I click the tab it brings me to the page within HTPC Manager but when I click the link on the NZBget page within HTPC Manager it will bring me to http://mydomain.com/nzbget instead of http://192.168.1.100:6789/nzbget? Do I have to use one of the rewrite functions in Apache?
You settings is all messed up.

Your url colliding because of your .conf
htpc manager is intended to have direct access to the apps, reverse proxy links is not supported (the link to webui will ALWAYS fail)
I dont know if you can use a rewrite rule, im not a apache guy,

You could use my fork tho, it supports reverse proxy links and it will do exactly what you want. (you will need to make sure that the urls dont collide)

My setup is:

htpcmanager: mydomain.com/htpc
sickrage: mydomain.com/sr
sabnzbd: mydomain.com/sab
etc
Awesome thanks! I'll give your fork a try and report back later.

edit: everything works as planned! Smile
^^
Everybody should update to the latest version ASAP as a huge security risk (my bad..) has been fixed.

The log page was not protected so even if you had set a username and password in HTPC-Manager anybody could have read your logs.

I would advice you to change passwords/apikeys