Krydos

The databases listed should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected databases. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

@cbapps Your topic has been split to http://www.helionet.org/index/topic/22536-cbapps-phpmyadmin/

Thanks! As a free service we don't have an advertising budget because we would rather invest all of the money that we do have into providing better service and improving the servers so we really appreciate the word of mouth recommendations that our satisfied users provide. Feel free to post about us on social media like twitter, facebook, hosting review sites, your personal websites or blogs, and anything else you can think of. As long as we have clients using our service Heliohost will continue to exist.

Try backing up the database, delete the database entirely, recreate it, and restore the data from the backup. I suspect that since InnoDB was broken for so long and was recently reenabled the old broken InnoDB tables are still causing you issues.

The database huulie_MUSICONLINEdevriendschap should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

I was able to create it just fine mysql> create table j25_update_sites_extensions (id int(6) unsigned auto_increment primary key, data varchar(30) not null); Query OK, 0 rows affected (0.07 sec) mysql> describe j25_update_sites_extensions; +-------+-----------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +-------+-----------------+------+-----+---------+----------------+ | id | int(6) unsigned | NO | PRI | NULL | auto_increment | | data | varchar(30) | NO | | NULL | | +-------+-----------------+------+-----+---------+----------------+ 2 rows in set (0.19 sec) mysql> drop table j25_update_sites_extensions; Query OK, 0 rows affected (0.01 sec) What database user are you using to try to create the table?

The database allmovie_wp should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

This is true. We don't normally keep backups for users automatically, but since we did a major upgrade on MySQL recently I manually took a backup of the databases prior to the upgrade. This time you're lucky and I can restore your database to the state it was before the upgrade, but wolstech is right we normally can't do anything for you. The database elaay_2013 should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The database nimb_cenicas should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The database nnicoles_phpex should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The database elaay_2013 should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The databases listed should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected databases. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The database amdc_amdc should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The database mng4_sviceDbX should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The database colette_joom25 should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

Thanks! As a free service we don't have an advertising budget because we would rather invest all of the money that we do have into providing better service and improving the servers so we really appreciate the word of mouth recommendations that our satisfied users provide. Feel free to post about us on social media like twitter, facebook, hosting review sites, your personal websites or blogs, and anything else you can think of. As long as we have clients using our service Heliohost will continue to exist.

To elaborate: Go to http://stevie.heliohost.org:2082/frontend/x3/passwd/index.html Type in your current password in the first box. Type in your new password twice even if it's the same as your current password. Make sure the box labeled "Synchronize MySQL Password" is checked. Click the button labeled "Change your password now!" Let us know if you're still having any issues accessing your data.

PhpMyAdmin Designer Mode has been enabled on Johnny. You can read the details on the news post here http://www.helionet.org/index/topic/22481-phpmyadmin-designer/ If it doesn't cause any issues on Johnny it will be enabled on Stevie as well.

Your password has been manually reset, tested, and emailed to your contact email address. mysql> select * from dispositivi; +----+----------------------------------+--------------------------------------+ | id | apikey | chiave | +----+----------------------------------+--------------------------------------+ | 3 | c286419dd7e831876f246c31ecece481 | 00000000-1c38-88b5-1599-90314fe98fb8 | +----+----------------------------------+--------------------------------------+ 1 row in set (0.00 sec) mysql> INSERT INTO dispositivi VALUES ('','933hjrih3rh','00000000-783j-u937-jks9'); ERROR 1366 (HY000): Incorrect integer value: '' for column 'id' at row 1 mysql> INSERT INTO dispositivi VALUES ('4','933hjrih3rh','00000000-783j-u937-jks9'); Query OK, 1 row affected (0.00 sec) mysql> select * from dispositivi; +----+----------------------------------+--------------------------------------+ | id | apikey | chiave | +----+----------------------------------+--------------------------------------+ | 3 | c286419dd7e831876f246c31ecece481 | 00000000-1c38-88b5-1599-90314fe98fb8 | | 4 | 933hjrih3rh | 00000000-783j-u937-jks9 | +----+----------------------------------+--------------------------------------+ 2 rows in set (0.00 sec) mysql> delete from dispositivi where id = '4'; Query OK, 1 row affected (0.00 sec) As you can see the user fedeener can select, insert, and delete from the table fedeener_marcatempo.dispositivi. However, the error is that it doesn't like the '' value for the id column. Let us know if you need any further assistance.

The paper_lantern theme has been enabled on the account paladox.

The database hosgar_nethunter should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

@hosgar Your topic has been split to http://www.helionet.org/index/topic/22479-invisible-databases-hosgar/

Please update this thread to let us know what they have to say about this. As wolstech mentioned it's not just you who has had this issue so it would be nice to know what to tell any users in the future that also come across this same thing. Thanks!

Thanks! As a free service we don't have an advertising budget because we would rather invest all of the money that we do have into providing better service and improving the servers so we really appreciate the word of mouth recommendations that our satisfied users provide. Feel free to post about us on social media like twitter, facebook, hosting review sites, your personal websites or blogs, and anything else you can think of. As long as we have clients using our service Heliohost will continue to exist.

Thanks! As a free service we don't have an advertising budget because we would rather invest all of the money that we do have into providing better service and improving the servers so we really appreciate the word of mouth recommendations that our satisfied users provide. Feel free to post about us on social media like twitter, facebook, hosting review sites, your personal websites or blogs, and anything else you can think of. As long as we have clients using our service Heliohost will continue to exist.