Postgres Access Control in Oregon

1

From rynar:

PostgreSQL in Oregon Region does not work properly when only its own Global IP is specified in “Access Control”, because it is rejected.

Input example: “xxx.xxx.xxx.xxx/32”.

It is possible to connect by adding “0.0.0.0/0”.

By the way, it works fine in Frankfurt Region.

Also, although “0.0.0.0/0” is included in the initial value, the actual initial behavior is to reject everything.

If you change the string appropriately and apply “0.0.0.0/0” again, you will get the expected behavior for the first time.

This seems to be a bit confusing.

2

@anurag Thank you for reprinting this from feedback.

Probably related: Access control with single IP SSL Error

2 Likes
3

We have confirmed that this issue has been resolved along with the following issues
Thanks to the render team.

2 Likes