Project

General

Profile

After upgrading to 4.1 from 3.9 browser shows a white page (Downgrade not possible?)

Added by of Montreal about 9 years ago

I did an upgrade from 3.9 to 4.1 a few days ago, and now when trying to configure tvheadend i only get a white page. Sourcecode of the displayed white page is this:


<html>
<head>
<meta name="apple-itunes-app" content="app-id=638900112">
<link rel="stylesheet" type="text/css" href="static/tvh.css.gz"/>
<script type="text/javascript" src="redir/locale.js"></script>
<script type="text/javascript" src="static/tvh.js.gz"></script>
<script type="text/javascript">
Ext.BLANK_IMAGE_URL = 'static/extjs/resources/images/default/s.gif';
Ext.onReady(tvheadend.app.init, tvheadend.app);
</script>
<style type="text/css">
html, body {
    font:normal 12px verdana;
    margin:0;
    padding:0;
    border:0 none;
    overflow:hidden;
    height:100%;
}
#systemlog {
    font:normal 12px courier; font-weight: bold;
}
p {
    margin:5px;
}
</style>
<title>HTS Tvheadend 4.1-374~g2218885-dirty</title>
</head>
<body>
<div id="systemlog"></div>
</body></html>

Any idea what i have to do here?

Same problem applies to 4.1-415~geab75c2
Sadly i can't downgrade because it seems like the configs aren't compatible then.


Replies (6)

RE: After upgrading to 4.1 from 3.9 browser shows a white page (Downgrade not possible?) - Added by Mark Clarkstone about 9 years ago

of Montreal wrote:

I did an upgrade from 3.9 to 4.1 a few days ago, and now when trying to configure tvheadend i only get a white page. Sourcecode of the displayed white page is this:

[...]

Any idea what i have to do here?

Same problem applies to 4.1-415~geab75c2
Sadly i can't downgrade because it seems like the configs aren't compatible then.

Look at your browser dev tools (in chrome its F12 - you may need to refresh) for any javascript errors & paste the results in a new bug issue on this site.

Bold: you should be able to downgrade provided you have a backup look in /home/hts/.hts/tvheadend/backup. (provided you installed it using a package manager)

RE: After upgrading to 4.1 from 3.9 browser shows a white page (Downgrade not possible?) - Added by of Montreal about 9 years ago

The console reports multiple errors:

http://192.168.1.11:9981/static/tvh.css.gz Failed to load resource: the server responded with a status of 500 (Unknown Code)
http://192.168.1.11:9981/static/tvh.js.gz Failed to load resource: the server responded with a status of 500 (Unknown Code)
extjs.html:8 Uncaught ReferenceError: Ext is not defined
http://192.168.1.11:9981/static/tvh.css.gz Failed to load resource: the server responded with a status of 500 (Unknown Code)

Seems like i have a backup for 3.9, will try that, but i would love to use the newer version of course.

RE: After upgrading to 4.1 from 3.9 browser shows a white page (Downgrade not possible?) - Added by Mark Clarkstone about 9 years ago

of Montreal wrote:

The console reports multiple errors:

[...]

Seems like i have a backup for 3.9, will try that, but i would love to use the newer version of course.

500 is a server error, I've never seen that before, try with a clean config (empty the /home/hts/.hts/tvheadend folder, MOVE YOUR BACKUPS FIRST!) & retest, if it fails again you'll need to run Tvheadend with debugging to find out why.

RE: After upgrading to 4.1 from 3.9 browser shows a white page (Downgrade not possible?) - Added by of Montreal about 9 years ago

I removed everything in the /.hts/tvheadend folder and still get the same errors (Some new config files get generated). Could it be some wrong rights to my files? Will try to find out how to run in debug mode now.

RE: After upgrading to 4.1 from 3.9 browser shows a white page (Downgrade not possible?) - Added by Jaroslav Kysela about 9 years ago

It's something with the resources. Usually, they're in /usr/local/share/tvheadend tree.. Check priviledges or build tvh with --enable-bundle .

RE: After upgrading to 4.1 from 3.9 browser shows a white page (Downgrade not possible?) - Added by of Montreal about 9 years ago

Building with --enable-bundle did the trick, thank you!

    (1-6/6)