1.3.0 Wheezy > 1.3.1 Upgrade

    Upgrade when ok
    manually stopped services
    disabled all plugins - then had to use normal ports (already updated to 8443 on mine.
    errata - disabled php-APC line in wheezy docs - still only shows in 1.2 but still an issue for Wheezy users that upgraded to php5.5 manually.


    ran the installer
    no errors finished sucessfully
    admin panel would never load on any ports.


    All websites worked fine - didn't have time to dig deeper rolled back to 1.3.0 via shapshot.
    panel webserver never started back up it appears.


    which logs should I check on next attempt? so I can post more information?
    (other plan) move sites to fresh jessie install without too many customization - which seem to cause some of my issues!

    1.3.3 went smoothly.


    No issues.


    plugins - disabled all but panel redirect - left that one and upgraded.


    then upgraded - checking errata - currently have OS updated to 5.5 still have to remove wheezy line for APC in doc/Debian/packages-wheezy


    install no issues


    updated plugins - all current from panel redirect / server default page / lets encrypt / phpswitcher
    all working correctly.


    - issue with databases remains.. noticed in 1.3.0 - haven't checked if there is an issue I don't know know about..


    found in 1.3.0 - didn't report expected it might be reported / fixed / my install has/had an issue.


    • create new DB - add existing DB user
    • only shows [email protected] instead of listing user in drop down.

    have to select user and change based on alpha listing (i think) if you have multiple but not sure.


    image attached.


    beyond that issue - all is running correctly...

    Files

    Quote from viper_iii

    only shows [email protected] instead of listing user in drop down.

    That is not an email. The select box holds the users that were already created. The select box allow you to assign an already created SQL user to another database.



    In the select box, for each SQL user is showed:

    • The SQL username
    • The @ sign
    • The hostname from which the user is allowed to connect to the SQL server

    Indeed, you can have many users with the same name but for different hosts:

    • user1@localhost
    • user1@srv.domain.tld
    • user1@%
    • ...

    Note that the @ sign is only used in the interface as separator. Showing something like user1localhost wouldn't make any sense.


    Thread closed.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

    SSH key for online support
    Quote from viper_iii

    plugins - disabled all

    You must disable the plugins only when asked in the errata file ;)

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

    SSH key for online support