Internal Server Error when attempting to connect to external Postgres DB

Wappler Version: 5.2.6
Operating System : Windows 11
Server Model: NodeJS
Database Type: Postgres (External)
Hosting Type: Docker

Actual behavior

Connectivity with External Postgres DB fails.
tried with all sorts of queries, simple, custom

How to reproduce

  1. Create a Postgres DB (version 13/12.4) hosted on another server.
  2. In Wappler add a new connection for it. Direct, No SSH
  3. Query Tester works fine, when attempting to execute any query i get a 500 error as shown below:
    {"status":"500","code":"42601","message":"zero-length delimited identifier at or near \"\"\"\"","stack":"error: zero-length delimited identifier at or near \"\"\"\"\n at Parser.parseErrorMessage (/opt/node_app/node_modules/pg-protocol/dist/parser.js:287:98)\n at Parser.handlePacket (/opt/node_app/node_modules/pg-protocol/dist/parser.js:126:29)\n at Parser.parse (/opt/node_app/node_modules/pg-protocol/dist/parser.js:39:38)\n at Socket.<anonymous> (/opt/node_app/node_modules/pg-protocol/dist/index.js:11:42)\n at Socket.emit (node:events:513:28)\n at addChunk (node:internal/streams/readable:324:12)\n at readableAddChunk (node:internal/streams/readable:297:9)\n at Readable.push (node:internal/streams/readable:234:10)\n at TCP.onStreamRead (node:internal/stream_base_commons:190:23)"}

Resolved After setting the searchpath to public

What was your previous search path setting?

Its was Blank

Weird if it was blank then it shouldn’t include it as option.

And you didn’t use the searchpath option before?

Nope, never!

Fixed in Wappler 5.3.0

1 Like

This topic was automatically closed after 24 hours. New replies are no longer allowed.