Zum Inhalt

Kategorie: Software

Nextcloud Client Cannot Connect to Server

I’ve had a strange problem with a very hard to find solution after I set up my second Nextcloud Server, version 12.0.3. The Webinterface was working fine but the Nextcloud client couldn’t connect to the server.

In the Nextcloud log files the following error message was displayed:
Sabre\DAV\Exception\NotAuthenticated: No public access to this resource., No ‚Authorization: Basic‘ header found. Either the client didn’t send one, or the server is misconfigured, No ‚Authorization: Bearer‘ header found. Either the client didn’t send one, or the server is mis-configured, No ‚Authorization: Basic‘ header found. Either the client didn’t send one, or the server is misconfigured

[internal function] Sabre\DAV\Auth\Plugin->beforeMethod(Object(Sabre\HTTP\Request), Object(Sabre\HTTP\Response))
/var/www/vhosts/vault111.de/nextcloud.vault111.de/3rdparty/sabre/event/lib/EventEmitterTrait.php – line 105: call_user_func_array(Array, Array)
/var/www/vhosts/vault111.de/nextcloud.vault111.de/3rdparty/sabre/dav/lib/DAV/Server.php – line 466: Sabre\Event\EventEmitter->emit(‚beforeMethod‘, Array)
/var/www/vhosts/vault111.de/nextcloud.vault111.de/3rdparty/sabre/dav/lib/DAV/Server.php – line 254: Sabre\DAV\Server->invokeMethod(Object(Sabre\HTTP\Request), Object(Sabre\HTTP\Response))
/var/www/vhosts/vault111.de/nextcloud.vault111.de/apps/dav/lib/Server.php – line 258: Sabre\DAV\Server->exec()
/var/www/vhosts/vault111.de/nextcloud.vault111.de/apps/dav/appinfo/v2/remote.php – line 33: OCA\DAV\Server->exec()
/var/www/vhosts/vault111.de/nextcloud.vault111.de/remote.php – line 162: require_once(‚/var/www/vhosts…‘)
{main}

The problem could be solved by adding the following line in the Apache vhost config:
SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1

Fixing Playback Crashes in Magix Vegas Pro

So it seems that Vegas Pro has some serious issues when it comes to multicore playback. I have experienced a lot of crashes during simple playback until I found a solution which fixed that (at least for me) and here’s what I did:

  • Open Vegas Pro
  • Click on Options
  • Press Shift+CMD and then click on Preferences

You will now see a new tab in the preferences menu called Intern.

  • Choose the tab Intern
  • Search for „multicore“
  • Set Enable multi-core rendering for playback to FALSE.

I didn’t have any crashes since I switched this. 🙂

Piwik Upgrade von Version 2 auf 3 schlägt wegen MySQL Problemen fehl

Wenn ihr euer Piwik 2 auf Version 3 upgraden wollt lauft ihr unter Umständen in Probleme beim Updaten der MySQL Datenbank rein und der Prozess bricht ab. Dies wird durch eine fehlende Tabelle und eine fehlende Spalte in einer Tabelle verursacht. Hier ist ein Beispiel, wie man das Problem lösen kann, basierend auf einer Piwik 2 Installation auf einem Server mit Plesk 17. Wie immer, denkt daran, dass ihr ein Backup von eurer Datenbank macht, bevor ihr darin händisch etwas verändert.

Die erste Fehlermeldung, die ihr bekommt lautet:

Kritischer Fehler während der Aktualisierung:
SQLSTATE[42S02]: Base table or view not found: 1146 Table ‚piwik_d.plugin_setting‘ doesn’t exist

Diese kann man lösen, in dem man die Tabelle manuell in der MySQL Datenbank erzeugt:

CREATE TABLE plugin_setting (
plugin_name VARCHAR(60) NOT NULL,
setting_name VARCHAR(255) NOT NULL,
setting_value LONGTEXT NOT NULL,
user_login VARCHAR(100) NOT NULL DEFAULT '',
INDEX(plugin_name, user_login)
) ENGINE=Innodb DEFAULT CHARSET=utf8

Wenn man danach den Upgrade Prozess noch einmal antriggert, erfolt eine zweite Fehlermeldung:

Kritischer Fehler während der Aktualisierung:
SQLSTATE[42S22]: Column not found: 1054 Unknown column ‚plugin_name‘ in ‚where clause‘

Da sich in meinem Fall keine Daten in der Tabelle befanden, konnte ich die Tabelle komplett droppen und einfach neu erzeugen:

CREATE TABLE site_setting (
idsite INTEGER(10) UNSIGNED NOT NULL,
plugin_name VARCHAR(60) NOT NULL,
setting_name VARCHAR(255) NOT NULL,
setting_value LONGTEXT NOT NULL,
INDEX(idsite, plugin_name)
) ENGINE=INNODB DEFAULT CHARSET=utf8

Falls sich Daten in der Tabelle befinden sollte, versucht die Spalte plugin_name manuell zu erzeugen, um das Problem zu beheben.

Das Upgrade sollte jetzt durchlaufen und danach könnt ihr Piwik 3 benutzen.

Piwik Upgrade from version 2 to 3 fails due to MySQL problems

If you want to upgrade your existing Piwik 2 installation to Piwik 3 you might run into different error messages during this process which will prevent you from performing the upgrade. This is caused by a missing table and a missing column in the existing database. Here is an example how to solve the problems based on a Piwik 2 Installation on Plesk 17. Please be sure to backup your database before performing any manual operations.

The first error you get is:

Kritischer Fehler während der Aktualisierung:
SQLSTATE[42S02]: Base table or view not found: 1146 Table ‚piwik_d.plugin_setting‘ doesn’t exist

This can be resolved by performing the following SQL query manually:

CREATE TABLE plugin_setting (
plugin_name VARCHAR(60) NOT NULL,
setting_name VARCHAR(255) NOT NULL,
setting_value LONGTEXT NOT NULL,
user_login VARCHAR(100) NOT NULL DEFAULT '',
INDEX(plugin_name, user_login)
) ENGINE=Innodb DEFAULT CHARSET=utf8

If you trigger the upgrade process again you might run into a second problem:

Kritischer Fehler während der Aktualisierung:
SQLSTATE[42S22]: Column not found: 1054 Unknown column ‚plugin_name‘ in ‚where clause‘

You can resolve this issue by dropping the table site_settings and create it completely new:

CREATE TABLE site_setting (
idsite INTEGER(10) UNSIGNED NOT NULL,
plugin_name VARCHAR(60) NOT NULL,
setting_name VARCHAR(255) NOT NULL,
setting_value LONGTEXT NOT NULL,
INDEX(idsite, plugin_name)
) ENGINE=INNODB DEFAULT CHARSET=utf8

In my case there was no data in this table so if you have data in it, don’t drop this table but try to add the column plugin_name manually.

After that the Piwik Upgrade should run through and you can use version 3 now.

Getting Cubase to Import Tempo of a MIDI file

I have been using Cubase quite a lot recently and exported my tracks created in Propellerhead Reason to MIDI and imported them in Cubase. Unfortunately Cubase doesn’t automatically adapt the tempo of your project if you import an MIDI file and it took me some time to find the option to change this.
Go to

  • File
  • Preferences
  • MIDI
  • MIDI File
  • Uncheck the option Ignore Master Track Events on Merge

cubase_midi

After that Cubase will also read the tempo from your MIDI file and adapt the tempo of your project accordingly.

Update to MySQL 5.6 on Debian 7 running Plesk 12.5

First of all, create a backup of your server or VM in case that anything will go wrong during the update process or any applications will not work anymore after updating your MySQL Server.

After that create a copy of your existing MySQL config as a backup:
cp /etc/mysql/my.cnf{,_original}

Now browse to http://dev.mysql.com/downloads/repo/apt/ and check which is the latest available MySQL version package. In our case mysql-apt-config_0.7.3-1_all.deb. Now log in to your server via SSH with root access. Download and install the tool:
wget http://dev.mysql.com/get/mysql-apt-config_0.7.3-1_all.deb
dpkg -i mysql-apt-config_0.7.3-1_all.deb

During the installation you will be asked which version you want to install so you can decide to update to MySQL 5.6 or 5.7.

After the installation wizard is finished, perform the following commands
apt-get update
apt-get install mysql-server

If you are being asked to update your my.cnf, select yes. That’s it.

The Monster – For Free

Digital Slate is offering their extreme dynamic processor VST plug-in for free. The only thing you will need to get it running is an iLok.

If you want to check out what The Monster can do for you, check this video from Steven Slate himself:

Update

If you are having problems registering your Monster using your iLok, I had the same problem and contacted the customer support. It seems that they „DoS“ed the iLok service. 🙂

Thank you for contacting Slate customer support. After an overwhelming, massive demand for The Monster, we managed to crash the iLok License servers. If you’ve already redeemed your Virtual Mix Rack/Revival/Trimmer license then you do not need to redeem the license again. Just install your Virtual Mix Rack 1.6.3.1 plugin and you’ll be good to go.

For those of you unable to register your license, we sincerely apologize for the delay. The iLok team is currently working on repairing this issue as we speak.

Thank you for your patience.

Install Seafile 5.1 on Debian 7.10 with Apache 2.2 and Plesk 10.5

Installing Seafile on a system that is maintained by Plesk can be a little bit tricky, especially if you are using Debian 7 with Apache 2.2. Therefore I wrote a small tutorial which will explain how to install seafile on a new created subdomain.

Requirements

Debian 7.10
Plesk 10.5
Domain set up with valid SSL Certificate