Re: My pgAdmin is broken - Mailing list pgadmin-support
I've updated the wheel on the download site to fix this. As an upgrade wouldn't fix existing installations, I just fixed it without bumping the version number. For users that have already installed, uninstalling pycrypto and pycryptodome and then reinstalling pycrypto is the correct fix.
On Thu, Apr 19, 2018 at 5:59 PM, Derek Ealy <derek.ealy@novawurks.com> wrote:
Well then thanks to Kushboo alsoOn Thu, Apr 19, 2018 at 9:09 AM, Isaias Sanchez <isaias.sanchez.l@gmail.com> wrote:The solution was thanks to Khushboo Vashi 'cause I reported this issue yesterday.
https://redmine.postgresql.org
/issues/3296
Let us know if it works for you.Derek Ealy wrote on 04/19/2018 04:04 PM:Allriiigghht Isaias!!!!!!!!!!Man thanks, I was so freakin' annoyed at this upgrade not working and how frustrating recovering from it was. I'm glad you figured out what the problem was, I had never even heard of pycrypto before to day.AwesomesauceOn Thu, Apr 19, 2018 at 8:57 AM, Isaias Sanchez <isaias.sanchez.l@gmail.com> wrote:I also had this problem, but the issue is some incompatibilities in pycryptodome and pycrypto:
1. Install v3.0:
pip install ./pgadmin4-3.0-py2.py3-none-an
y.whl 2. Unistall pycryptodome:
pip uninstall pycryptodome
3. Uninstall/Install pgcrypto:
pip uninstall pycrypto
pip3 install pycrypto
4. Start pgadmin4:
python /usr/local/lib/python/site-pac
kages/pgadmin4/pgAdmin4.py & Go to: http://127.0.0.1:5050
After that v3.0 works just fine.
Cheers,
Isaias S.
Derek Ealy wrote on 04/19/2018 03:18 PM:A couple of days ago I tried upgrading to v3.0. This never worked for me. Normally I activate the python environment and then install the latest wheel file to upgrade. I was never able to login successfully on v3.0.So I gave up and tried to go back to v2.1, again I did so by reinstalling the v2.1 wheel file. However afterwards I can't launch pgAdmin. I get this error message:alembic.util.exc.CommandError: Can't locate revision identified by '50aad68f99c2'I've now burned several hours on trying to fix this. What is the best way to at least get back to a working system with v2.1? In the future is there some better way to upgrade or revert to a previous version when things go wrong?Thanks, Derek--dmeDerek EalySr. Software ArchitectNovaWurks, Inc.10772 Noel StreetLos Alamitos, CA 90720P: 562.340.6270F: 877.353.7537C: 310.936.4070........................................ CONFIDENTIALITY NOTICE: This e-mail, including attachments, is company confidential information proprietary to NovaWurks Corporation or its customers and may be confidential, legally privileged, and protected by law. If you are not the intended recipient you may not use, disclose, distribute, copy, print, or rely on this e-mail. If you have received this transmission in error please notify the sender and destroy the original transmission and its attachments without reading or saving. Thank you.--dmeDerek EalySr. Software ArchitectNovaWurks, Inc.10772 Noel StreetLos Alamitos, CA 90720P: 562.340.6270F: 877.353.7537C: 310.936.4070........................................ CONFIDENTIALITY NOTICE: This e-mail, including attachments, is company confidential information proprietary to NovaWurks Corporation or its customers and may be confidential, legally privileged, and protected by law. If you are not the intended recipient you may not use, disclose, distribute, copy, print, or rely on this e-mail. If you have received this transmission in error please notify the sender and destroy the original transmission and its attachments without reading or saving. Thank you.--dmeDerek EalySr. Software ArchitectNovaWurks, Inc.P: 562.340.6270F: 877.353.7537C: 310.936.4070........................................ CONFIDENTIALITY NOTICE: This e-mail, including attachments, is company confidential information proprietary to NovaWurks Corporation or its customers and may be confidential, legally privileged, and protected by law. If you are not the intended recipient you may not use, disclose, distribute, copy, print, or rely on this e-mail. If you have received this transmission in error please notify the sender and destroy the original transmission and its attachments without reading or saving. Thank you.
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
pgadmin-support by date: