Re: pgAdmin portal

[Akshay Joshi]

Hi

If I understand your problem correctly, pgAdmin4 runs in two-mode (Desktop
and Server). In Server mode, users can sign-in using their credentials, but
as the first step Administrator has permission to create new users (as
normal or admin). Once sign-in using that credentials user can see the
auto-discovered server and we have added *shared server support *
https://www.pgadmin.org/docs/pgadmin4/4.26/server_dialog.html.


On Thu, Oct 8, 2020 at 7:37 PM  wrote:

> Hello pgAdmin community,
>
> Is there a secure pgAdmin portal that can allow use of web based pgAdmin
> where users can register/sign-in and create accounts that can then allow
> access to PostgreSQL instances that are accessible on the internet via set
> credentials say via public IP as an alternative to pgAdmin installation on
> premise.
>
> Thank you in advance.
>
> Best regards,
>
> Charles
>


-- 
*Thanks & Regards*
*Akshay Joshi*
*pgAdmin Hacker | Sr. Software Architect*
*EDB Postgres *

*Mobile: +91 976-788-8246*

Re: v4.26, produces no output, errors in the log

[Akshay Joshi]

Hi Cherio

Have you execute the query or explain options (explain, explain analyze)?
These options are available on the toolbar, I have tested explain is
working fine for me on v4.26.
If possible please provide the SQL Query and Screenshots.

On Thu, Oct 8, 2020 at 11:25 PM Cherio  wrote:

> After reinstalling 4.26, clearing everything again and restarting the
> errors are gone, the data shows but the Explain tab is blank entirely.
> Those sub-tabs underneath are missing so there is no explain data
> whatsoever.
>
> The logs are clean.
>
> On Thu, Oct 8, 2020 at 1:29 PM Cherio  wrote:
>
>> I just upgraded pgAdmin from 4.24 to 4.26 (python wheel install) and
>> almost all result tabs are now blank.
>> Neither Query nor Explain produce any result. I cleared all chrome cache
>> (cookies, session/local storage), restarted the backend with no success.
>>
>> I rolled back to 4.24 and everything works as before.
>>
>> Version: 4.26
>> Copyright (C) 2013 - 2020, The pgAdmin Development Team
>> Python Version: 3.8.2 (default, Jul 16 2020, 14:00:26) [GCC 9.3.0]
>> Flask Version: 1.0.2
>> Application Mode: Desktop
>> Current User: pgadm...@pgadmin.org
>> OS: "20.04.1 LTS (Focal Fossa)"
>>
>> The log is a repetition of the same error (see below)
>>
>>
>> ===
>> 2020-10-08 12:25:39,125: ERROR  flask.app:  400 Bad Request: The CSRF
>> session token is missing.
>> Traceback (most recent call last):
>>   File
>> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
>> line 256, in protect
>> validate_csrf(self._get_csrf_token())
>>   File
>> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
>> line 94, in validate_csrf
>> raise ValidationError('The CSRF session token is missing.')
>> wtforms.validators.ValidationError: The CSRF session token is missing.
>>
>> During handling of the above exception, another exception occurred:
>>
>> Traceback (most recent call last):
>>   File
>> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask/app.py", line
>> 1811, in full_dispatch_request
>> rv = self.preprocess_request()
>>   File
>> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask/app.py", line
>> 2087, in preprocess_request
>> rv = func()
>>   File
>> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
>> line 224, in csrf_protect
>> self.protect()
>>   File
>> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
>> line 259, in protect
>> self._error_response(e.args[0])
>>   File
>> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
>> line 302, in _error_response
>> raise CSRFError(reason)
>> flask_wtf.csrf.CSRFError: 400 Bad Request: The CSRF session token is
>> missing.
>> 2020-10-08 13:01:37,714: ERROR  flask.app:  400 Bad Request: The CSRF
>> session token is missing.
>> Traceback (most recent call last):
>>   File
>> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
>> line 256, in protect
>> validate_csrf(self._get_csrf_token())
>>   File
>> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
>> line 94, in validate_csrf
>> raise ValidationError('The CSRF session token is missing.')
>> wtforms.validators.ValidationError: The CSRF session token is missing.
>>
>> During handling of the above exception, another exception occurred:
>>
>> Traceback (most recent call last):
>>   File
>> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask/app.py", line
>> 1811, in full_dispatch_request
>> rv = self.preprocess_request()
>>   File
>> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask/app.py", line
>> 2087, in preprocess_request
>> rv = func()
>>   File
>> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
>> line 224, in csrf_protect
>> self.protect()
>>   File
>> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
>> line 259, in protect
>> self._error_response(e.args[0])
>>   File
>> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
>> line 302, in _error_response
>> raise CSRFError(reason)
>> flask_wtf.csrf.CSRFError: 400 Bad Request: The CSRF session token is
>> missing.
>> 2020-10-08 13:01:42,712: ERROR  flask.app:  400 Bad Request: The CSRF
>> session token is missing.
>> Traceback (most recent call last):
>>   File
>> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
>> line 256, in protect
>> validate_csrf(self._get_csrf_token())
>>   File
>> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
>> line 94, in validate_csrf
>> raise ValidationError('The CSRF session token is missing.')
>> wtforms.validators.ValidationError: The CSRF session token is missing.
>>
>> During handling of the above exception, another exception occurred:
>>
>> Traceback (most recent call last):
>>   File
>> "/home/user/opt/pgadmin4/lib/python3.8/

Question about open source license

[markpare]

Hi team, I was wondering about your open source license. If I take the
source and extend it with some non-PostgreSQL related ideas, am I free to
sell that final product? Do I have to make sure that my code is also open
source?

 

I read about the copyleft definition, but wasn't sure what applied to your
license.

 

 

Let me know - thanks!

 

problem installation

[אביחי קקון]

hii,
 I have problem in the installation and show me message :
what i do?
[image: INSTALL.PNG]

Re: v4.26, produces no output, errors in the log

[Cherio]

After reinstalling 4.26, clearing everything again and restarting the
errors are gone, the data shows but the Explain tab is blank entirely.
Those sub-tabs underneath are missing so there is no explain data
whatsoever.

The logs are clean.

On Thu, Oct 8, 2020 at 1:29 PM Cherio  wrote:

> I just upgraded pgAdmin from 4.24 to 4.26 (python wheel install) and
> almost all result tabs are now blank.
> Neither Query nor Explain produce any result. I cleared all chrome cache
> (cookies, session/local storage), restarted the backend with no success.
>
> I rolled back to 4.24 and everything works as before.
>
> Version: 4.26
> Copyright (C) 2013 - 2020, The pgAdmin Development Team
> Python Version: 3.8.2 (default, Jul 16 2020, 14:00:26) [GCC 9.3.0]
> Flask Version: 1.0.2
> Application Mode: Desktop
> Current User: pgadm...@pgadmin.org
> OS: "20.04.1 LTS (Focal Fossa)"
>
> The log is a repetition of the same error (see below)
>
>
> ===
> 2020-10-08 12:25:39,125: ERROR  flask.app:  400 Bad Request: The CSRF
> session token is missing.
> Traceback (most recent call last):
>   File
> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
> line 256, in protect
> validate_csrf(self._get_csrf_token())
>   File
> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
> line 94, in validate_csrf
> raise ValidationError('The CSRF session token is missing.')
> wtforms.validators.ValidationError: The CSRF session token is missing.
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask/app.py",
> line 1811, in full_dispatch_request
> rv = self.preprocess_request()
>   File "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask/app.py",
> line 2087, in preprocess_request
> rv = func()
>   File
> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
> line 224, in csrf_protect
> self.protect()
>   File
> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
> line 259, in protect
> self._error_response(e.args[0])
>   File
> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
> line 302, in _error_response
> raise CSRFError(reason)
> flask_wtf.csrf.CSRFError: 400 Bad Request: The CSRF session token is
> missing.
> 2020-10-08 13:01:37,714: ERROR  flask.app:  400 Bad Request: The CSRF
> session token is missing.
> Traceback (most recent call last):
>   File
> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
> line 256, in protect
> validate_csrf(self._get_csrf_token())
>   File
> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
> line 94, in validate_csrf
> raise ValidationError('The CSRF session token is missing.')
> wtforms.validators.ValidationError: The CSRF session token is missing.
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask/app.py",
> line 1811, in full_dispatch_request
> rv = self.preprocess_request()
>   File "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask/app.py",
> line 2087, in preprocess_request
> rv = func()
>   File
> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
> line 224, in csrf_protect
> self.protect()
>   File
> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
> line 259, in protect
> self._error_response(e.args[0])
>   File
> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
> line 302, in _error_response
> raise CSRFError(reason)
> flask_wtf.csrf.CSRFError: 400 Bad Request: The CSRF session token is
> missing.
> 2020-10-08 13:01:42,712: ERROR  flask.app:  400 Bad Request: The CSRF
> session token is missing.
> Traceback (most recent call last):
>   File
> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
> line 256, in protect
> validate_csrf(self._get_csrf_token())
>   File
> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
> line 94, in validate_csrf
> raise ValidationError('The CSRF session token is missing.')
> wtforms.validators.ValidationError: The CSRF session token is missing.
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask/app.py",
> line 1811, in full_dispatch_request
> rv = self.preprocess_request()
>   File "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask/app.py",
> line 2087, in preprocess_request
> rv = func()
>   File
> "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
> line 224, in csrf_protect
> self.protect()
>   File
> "/home/user/opt/pgadmin4/lib/python3.8/site-package

v4.26, produces no output, errors in the log

[Cherio]

I just upgraded pgAdmin from 4.24 to 4.26 (python wheel install) and almost
all result tabs are now blank.
Neither Query nor Explain produce any result. I cleared all chrome cache
(cookies, session/local storage), restarted the backend with no success.

I rolled back to 4.24 and everything works as before.

Version: 4.26
Copyright (C) 2013 - 2020, The pgAdmin Development Team
Python Version: 3.8.2 (default, Jul 16 2020, 14:00:26) [GCC 9.3.0]
Flask Version: 1.0.2
Application Mode: Desktop
Current User: pgadm...@pgadmin.org
OS: "20.04.1 LTS (Focal Fossa)"

The log is a repetition of the same error (see below)


===
2020-10-08 12:25:39,125: ERROR  flask.app:  400 Bad Request: The CSRF
session token is missing.
Traceback (most recent call last):
  File
"/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
line 256, in protect
validate_csrf(self._get_csrf_token())
  File
"/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
line 94, in validate_csrf
raise ValidationError('The CSRF session token is missing.')
wtforms.validators.ValidationError: The CSRF session token is missing.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask/app.py",
line 1811, in full_dispatch_request
rv = self.preprocess_request()
  File "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask/app.py",
line 2087, in preprocess_request
rv = func()
  File
"/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
line 224, in csrf_protect
self.protect()
  File
"/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
line 259, in protect
self._error_response(e.args[0])
  File
"/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
line 302, in _error_response
raise CSRFError(reason)
flask_wtf.csrf.CSRFError: 400 Bad Request: The CSRF session token is
missing.
2020-10-08 13:01:37,714: ERROR  flask.app:  400 Bad Request: The CSRF
session token is missing.
Traceback (most recent call last):
  File
"/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
line 256, in protect
validate_csrf(self._get_csrf_token())
  File
"/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
line 94, in validate_csrf
raise ValidationError('The CSRF session token is missing.')
wtforms.validators.ValidationError: The CSRF session token is missing.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask/app.py",
line 1811, in full_dispatch_request
rv = self.preprocess_request()
  File "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask/app.py",
line 2087, in preprocess_request
rv = func()
  File
"/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
line 224, in csrf_protect
self.protect()
  File
"/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
line 259, in protect
self._error_response(e.args[0])
  File
"/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
line 302, in _error_response
raise CSRFError(reason)
flask_wtf.csrf.CSRFError: 400 Bad Request: The CSRF session token is
missing.
2020-10-08 13:01:42,712: ERROR  flask.app:  400 Bad Request: The CSRF
session token is missing.
Traceback (most recent call last):
  File
"/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
line 256, in protect
validate_csrf(self._get_csrf_token())
  File
"/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
line 94, in validate_csrf
raise ValidationError('The CSRF session token is missing.')
wtforms.validators.ValidationError: The CSRF session token is missing.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask/app.py",
line 1811, in full_dispatch_request
rv = self.preprocess_request()
  File "/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask/app.py",
line 2087, in preprocess_request
rv = func()
  File
"/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
line 224, in csrf_protect
self.protect()
  File
"/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
line 259, in protect
self._error_response(e.args[0])
  File
"/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
line 302, in _error_response
raise CSRFError(reason)
flask_wtf.csrf.CSRFError: 400 Bad Request: The CSRF session token is
missing.
2020-10-08 13:01:44,035: ERROR  flask.app:  400 Bad Request: The CSRF
session token is missing.
Traceback (most recent call last):
  File
"/home/user/opt/pgadmin4/lib/python3.8/site-packages/flask_wtf/csrf.py",
line 2

pgAdmin portal

[cwaweru]

Hello pgAdmin community,Is there a secure pgAdmin portal that can allow use of web based pgAdmin where users can register/sign-in and create accounts that can then allow access to PostgreSQL instances that are accessible on the internet via set credentials say via public IP as an alternative to pgAdmin installation on premise.Thank you in advance.Best regards,Charles

Problem getting https working

[Ian Moore]

HI,
I've been trying to get pgAdmin 4 4.26 working with https and not having
any success. If I don't use https, it all works perfectly.

I've followed the instructions at
https://www.pgadmin.org/docs/pgadmin4/development/container_deployment.html#
and also found some info on this list in the thread
https://www.postgresql.org/message-id/1b4bba2d-910d-3017-bc5d-6b45dcac31d0%40empirica-systeme.de

I've used this config, which the same as that given in the above thread as
a known working config:
docker run -p 554:443 -v
'/etc/apache2/ssl.crt/server.crt:/certs/server.cert' -v
'/etc/apache2/ssl.key/server.key:/certs/server.key' -e
'PGADMIN_DEFAULT_EMAIL=pgad...@server.com' -e
'PGADMIN_DEFAULT_PASSWORD=mysecurepassword' -e 'PGADMIN_ENABLE_TLS=True' -e
'PGADMIN_SERVER_NAME=myserver.com' -d dpage/pgadmin4

The ssl cert & key are used on the host server to host run a website with
apache on ports 80 & 443 (hence the docker port 443 is re-directed to 554),
so they are valid and I've confirmed that the docker is picking them up
correctly by copying them from the running docker back to the host machine
& comparing them with the originals and they are exactly the same.

The output of docker ps is:
CONTAINER IDIMAGE   COMMAND CREATED
STATUS  PORTS  NAMES
c2c4cc713c3adpage/pgadmin4  "/entrypoint.sh"17 minutes ago
 Up 17 minutes   80/tcp, 0.0.0.0:554->443/tcp   youthful_ptolemy

When I try to access pgAdmin in my browser using https://myserver.com:554
or https://myserverip:554 or https://127.0.0.1:554, I get this response:
Secure Connection Failed

An error occurred during a connection to intranet.threedradio.com:8443.
PR_CONNECT_RESET_ERROR

If I telnet to the server on port 554, it connects briefly and then closes
the connection, so it's definitely listening on the correct port.

I also tried redirecting port 80 to another port in case that was causing a
conflict with apache, but that didn't seem to help at all.

Hoping someone can help!

Cheers,
Ian