Thread: [pgadmin-support] internal server error on password change
Hi
--
I just got pgAdmin4 1.2 running in server mode today, by and large it seems to be ok (but a little flakey).
My devs are unable to change their (pgAdmin) passwords. I created individual accounts for them using their email addresses and supplied a standard password. When they go to the change password link and enter a new password an Internal Server Error message is returned and the password isn't changed.
I can change their passwords myself (as an Admin) but that isn't really what we want to do here. Any ideas what is wrong or how to fix this?
We can't upgrade to 1.3 because that doesn't work at all.
Ubuntu 16.04 Server
Python 2.7 in Pip
Apache 2 with mod_wsgi
Thanks, Derek
dme
Derek Ealy
Sr. Software Architect
NovaWurks, Inc.
10772 Noel Street
Los Alamitos, CA 90720
P: 562.340.6270
F: 877.353.7537
C: 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.
On Tue, Mar 14, 2017 at 4:54 AM, Derek Ealy <derek.ealy@novawurks.com> wrote:
HiI just got pgAdmin4 1.2 running in server mode today, by and large it seems to be ok (but a little flakey).My devs are unable to change their (pgAdmin) passwords. I created individual accounts for them using their email addresses and supplied a standard password. When they go to the change password link and enter a new password an Internal Server Error message is returned and the password isn't changed.I can change their passwords myself (as an Admin) but that isn't really what we want to do here. Any ideas what is wrong or how to fix this?
Murtuza - can you please take a look at this?
Looks like a bug to me.
Derek,
Can you please share pgadmin log file for more analysis?
We can't upgrade to 1.3 because that doesn't work at all.Ubuntu 16.04 ServerPython 2.7 in PipApache 2 with mod_wsgiThanks, 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.
There is also something wrong with version 1.3. I can't get it to work either on the desktop or server mode. It always shows a popup with some sort of script error. So when using v1.2 we always have that annoying popup saying 1.3 is available, is there any way to turn that off?
You're system won't allow me to email the smallest pgadmin.log file (> 200kB), so I put it up on pastebin.
Here is the pgadmin.log on pastebin: http://pastebin.com/TWNQwbRS
I've attached the apache access and error logs
On Mon, Mar 13, 2017 at 10:23 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
On Tue, Mar 14, 2017 at 4:54 AM, Derek Ealy <derek.ealy@novawurks.com> wrote:
HiI just got pgAdmin4 1.2 running in server mode today, by and large it seems to be ok (but a little flakey).My devs are unable to change their (pgAdmin) passwords. I created individual accounts for them using their email addresses and supplied a standard password. When they go to the change password link and enter a new password an Internal Server Error message is returned and the password isn't changed.I can change their passwords myself (as an Admin) but that isn't really what we want to do here. Any ideas what is wrong or how to fix this?Murtuza - can you please take a look at this?Looks like a bug to me.Derek,Can you please share pgadmin log file for more analysis?We can't upgrade to 1.3 because that doesn't work at all.Ubuntu 16.04 ServerPython 2.7 in PipApache 2 with mod_wsgiThanks, 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.
dme
Derek Ealy
Sr. Software Architect
NovaWurks, Inc.
10772 Noel Street
Los Alamitos, CA 90720
P: 562.340.6270
F: 877.353.7537
C: 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.
Attachment
I've gone through the apache access log and I see that send_password_change_notice in changeble.py looks like it is trying to send an email and this ultimately is causing the error. It looks like it is trying to send it via the web browser and the client machine. This eventually tries to open a socket and gets a connection refused.
Not sure why the server is trying to open a connection to the client machine that is running the browser, but it appears to me that doing so results in a connection refused error
On Tue, Mar 14, 2017 at 7:51 AM, Derek Ealy <derek.ealy@novawurks.com> wrote:
There is also something wrong with version 1.3. I can't get it to work either on the desktop or server mode. It always shows a popup with some sort of script error. So when using v1.2 we always have that annoying popup saying 1.3 is available, is there any way to turn that off?You're system won't allow me to email the smallest pgadmin.log file (> 200kB), so I put it up on pastebin.Here is the pgadmin.log on pastebin: http://pastebin.com/TWNQwbRS I've attached the apache access and error logsOn Mon, Mar 13, 2017 at 10:23 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
On Tue, Mar 14, 2017 at 4:54 AM, Derek Ealy <derek.ealy@novawurks.com> wrote:
HiI just got pgAdmin4 1.2 running in server mode today, by and large it seems to be ok (but a little flakey).My devs are unable to change their (pgAdmin) passwords. I created individual accounts for them using their email addresses and supplied a standard password. When they go to the change password link and enter a new password an Internal Server Error message is returned and the password isn't changed.I can change their passwords myself (as an Admin) but that isn't really what we want to do here. Any ideas what is wrong or how to fix this?Murtuza - can you please take a look at this?Looks like a bug to me.Derek,Can you please share pgadmin log file for more analysis?We can't upgrade to 1.3 because that doesn't work at all.Ubuntu 16.04 ServerPython 2.7 in PipApache 2 with mod_wsgiThanks, 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.
dme
Derek Ealy
Sr. Software Architect
NovaWurks, Inc.
10772 Noel Street
Los Alamitos, CA 90720
P: 562.340.6270
F: 877.353.7537
C: 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.
Hi Derek,
By default, pgAdmin4 will try to send notification email for password change to the respective user.
There are two ways to handle this scenario,
1) You can disable password notifications by adding below configuration options in "config_local.py" file (under "pgAdmin4" root directory).
SECURITY_SEND_REGISTER_EMAIL = False
SECURITY_SEND_PASSWORD_CHANGE_EMAIL = False
SECURITY_SEND_PASSWORD_RESET_NOTICE_EMAIL = False
2) If you want that your pgAdmin4 user gets notification then configure your SMTP settings in "config_local.py" file(under "pgAdmin4" root directory) so that pgAdmin4 can send notification emails to users regarding their password change/reset events.
MAIL_SERVER = 'localhost'
MAIL_PORT = 25
MAIL_USE_SSL = False
MAIL_USE_TLS = False
MAIL_USERNAME = ''
MAIL_PASSWORD = ''
--
Regards,
On Tue, Mar 14, 2017 at 8:37 PM, Derek Ealy <derek.ealy@novawurks.com> wrote:
I've gone through the apache access log and I see that send_password_change_notice in changeble.py looks like it is trying to send an email and this ultimately is causing the error. It looks like it is trying to send it via the web browser and the client machine. This eventually tries to open a socket and gets a connection refused.Not sure why the server is trying to open a connection to the client machine that is running the browser, but it appears to me that doing so results in a connection refused errorOn Tue, Mar 14, 2017 at 7:51 AM, Derek Ealy <derek.ealy@novawurks.com> wrote:There is also something wrong with version 1.3. I can't get it to work either on the desktop or server mode. It always shows a popup with some sort of script error. So when using v1.2 we always have that annoying popup saying 1.3 is available, is there any way to turn that off?You're system won't allow me to email the smallest pgadmin.log file (> 200kB), so I put it up on pastebin.Here is the pgadmin.log on pastebin: http://pastebin.com/TWNQwbRS I've attached the apache access and error logsOn Mon, Mar 13, 2017 at 10:23 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
On Tue, Mar 14, 2017 at 4:54 AM, Derek Ealy <derek.ealy@novawurks.com> wrote:
HiI just got pgAdmin4 1.2 running in server mode today, by and large it seems to be ok (but a little flakey).My devs are unable to change their (pgAdmin) passwords. I created individual accounts for them using their email addresses and supplied a standard password. When they go to the change password link and enter a new password an Internal Server Error message is returned and the password isn't changed.I can change their passwords myself (as an Admin) but that isn't really what we want to do here. Any ideas what is wrong or how to fix this?Murtuza - can you please take a look at this?Looks like a bug to me.Derek,Can you please share pgadmin log file for more analysis?We can't upgrade to 1.3 because that doesn't work at all.Ubuntu 16.04 ServerPython 2.7 in PipApache 2 with mod_wsgiThanks, 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.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.
Great thanks, that seems to be working now.
On Wed, Mar 15, 2017 at 12:43 AM, Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com> wrote:
Hi Derek,By default, pgAdmin4 will try to send notification email for password change to the respective user.There are two ways to handle this scenario,1) You can disable password notifications by adding below configuration options in "config_local.py" file (under "pgAdmin4" root directory).SECURITY_SEND_REGISTER_EMAIL = FalseSECURITY_SEND_PASSWORD_CHANGE_EMAIL = False SECURITY_SEND_PASSWORD_RESET_NOTICE_EMAIL = False 2) If you want that your pgAdmin4 user gets notification then configure your SMTP settings in "config_local.py" file(under "pgAdmin4" root directory) so that pgAdmin4 can send notification emails to users regarding their password change/reset events.MAIL_SERVER = 'localhost'MAIL_PORT = 25MAIL_USE_SSL = FalseMAIL_USE_TLS = FalseMAIL_USERNAME = ''MAIL_PASSWORD = ''--Regards,On Tue, Mar 14, 2017 at 8:37 PM, Derek Ealy <derek.ealy@novawurks.com> wrote:I've gone through the apache access log and I see that send_password_change_notice in changeble.py looks like it is trying to send an email and this ultimately is causing the error. It looks like it is trying to send it via the web browser and the client machine. This eventually tries to open a socket and gets a connection refused.Not sure why the server is trying to open a connection to the client machine that is running the browser, but it appears to me that doing so results in a connection refused errorOn Tue, Mar 14, 2017 at 7:51 AM, Derek Ealy <derek.ealy@novawurks.com> wrote:There is also something wrong with version 1.3. I can't get it to work either on the desktop or server mode. It always shows a popup with some sort of script error. So when using v1.2 we always have that annoying popup saying 1.3 is available, is there any way to turn that off?You're system won't allow me to email the smallest pgadmin.log file (> 200kB), so I put it up on pastebin.Here is the pgadmin.log on pastebin: http://pastebin.com/TWNQwbRS I've attached the apache access and error logsOn Mon, Mar 13, 2017 at 10:23 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
On Tue, Mar 14, 2017 at 4:54 AM, Derek Ealy <derek.ealy@novawurks.com> wrote:
HiI just got pgAdmin4 1.2 running in server mode today, by and large it seems to be ok (but a little flakey).My devs are unable to change their (pgAdmin) passwords. I created individual accounts for them using their email addresses and supplied a standard password. When they go to the change password link and enter a new password an Internal Server Error message is returned and the password isn't changed.I can change their passwords myself (as an Admin) but that isn't really what we want to do here. Any ideas what is wrong or how to fix this?Murtuza - can you please take a look at this?Looks like a bug to me.Derek,Can you please share pgadmin log file for more analysis?We can't upgrade to 1.3 because that doesn't work at all.Ubuntu 16.04 ServerPython 2.7 in PipApache 2 with mod_wsgiThanks, 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.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.
dme
Derek Ealy
Sr. Software Architect
NovaWurks, Inc.
10772 Noel Street
Los Alamitos, CA 90720
P: 562.340.6270
F: 877.353.7537
C: 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.