Hello !
When I want activate my new server with my API key, the key is accept but no unlock the PRO fonctions.
Wky ?
Hello !
When I want activate my new server with my API key, the key is accept but no unlock the PRO fonctions.
Wky ?
Hi Mattymatt,
Are you able to confirm if when running:
sudo su -
qb api
That it shows the API as active? (Please don’t upload the output of that here)
yes :
Status: active
Total Activations Purchased: 1
Total Acitvations Used: 1
Activations Remaining: 0
Activated: true
And what happens if you run:
sudo su -
qb fix version
done !
✓ QuickBox Pro Update Completed.
but now I have " 502 Bad Gateway" with my web navigator
Alright, now if you try:
sudo su -
service php7.3-fpm restart && service nginx restart
And we’ll see if that brings it up
Failed to restart php7.3-fpm.service: Unit php7.3-fpm.service not found.
This is most likely caused by out of date packages in that case.
sudo su -
apt update && apt upgrade -y
qb fix version
no … it’s the same
➜ Applying PHP Tweaks…
sed: can’t read /etc/php/7.3/fpm/pool.d/www.conf: No such file or directory
✓ PHP Tweaks Applied.
➜ Enabling qb autocomplete…
✓ qb autocomplete enabled.
php7.3-fpm: unrecognized service
Failed to restart php7.3-fpm.service: Unit php7.3-fpm.service not found.
➜ Cleaning Installation Files…
php7.3-fpm: unrecognized service
Failed to restart php7.3-fpm.service: Unit php7.3-fpm.service not found.
✓ QuickBox Pro Update Completed.
Will you try running the following:
sudo su -
qb fix dpkg
Then run:
QB_BASEDEPS='php7.3 php7.3-cli php7.3-curl php7.3-fpm php7.3-gd php7.3-geoip php7.3-json php-memcached php7.3-mbstring php7.3-msgpack php7.3-mysql php7.3-opcache php7.3-xml php7.3-xmlrpc php7.3-zip'
apt-get install -y ${QB_BASEDEPS}
At this point, you can try starting the service with service php7.3-fpm restart
and then try to run another qb fix version
just for good measure.
The updater in theory would be handling this for you, however, it seems like since your php services are missing, it didn’t port in the proper dependencies, this is usually a sign of a dpkg lock on the apt database.
YES ! all is goot now !
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.