ORDS, SODA & JSON in the Database

Hi experts,
We've recently upgraded Production ORDS from 19.2.0.r1991647 to 20.2.1.r2270350.
We have Nginx to make ssl and redirect and it was working nice with this config file. No changes during ORDS upgrade:

# For more information on configuration, see:
#   * Official English Documentation: http://nginx.org/en/docs/
#   * Official Russian Documentation: http://nginx.org/ru/docs/

user nginx;
worker_processes auto;
error_log /var/log/nginx/error.log;
pid /run/nginx.pid;

# Load dynamic modules. See /usr/share/doc/nginx/README.dynamic.
include /usr/share/nginx/modules/*.conf;

events {
  worker_connections 1024;
}

http {
  log_format main '$remote_addr - $remote_user [$time_local] "$request" '
           '$status $body_bytes_sent "$http_referer" '
           '"$http_user_agent" "$http_x_forwarded_for"';

  access_log /var/log/nginx/access.log main;

  sendfile      on;
  tcp_nopush     on;
  tcp_nodelay     on;
  keepalive_timeout  65;
  types_hash_max_size 2048;

  include       /etc/nginx/mime.types;
  default_type    application/octet-stream;

  # Load modular configuration files from the /etc/nginx/conf.d directory.
    # See http://nginx.org/en/docs/ngx_core_module.html#include
  # for more information.
  include /etc/nginx/conf.d/*.conf;

#JRA Comment access to 80
#  server {
#    listen    80 default_server;
#    listen    [::]:80 default_server;
#    server_name _;
#    root     /usr/share/nginx/html;
#
#    # Load configuration files for the default server block.
#    include /etc/nginx/default.d/*.conf;
#
#    location / {
#    }
#
#    error_page 404 /404.html;
#      location = /40x.html {
#    }
#
#    error_page 500 502 503 504 /50x.html;
#      location = /50x.html {
#    }
#  }

#JRA Redirect all traffic to 443
server {
  listen 80 default_server;

  server_name _;

    return 301 https://$host$request_uri;
}

# Settings for a TLS enabled server.
#
  server {
    listen    443 ssl http2 default_server;
    listen    [::]:443 ssl http2 default_server;
    server_name _;
    root     /usr/share/nginx/html;
#JRA: Customer SSL certificate
    ssl_certificate "/root/.ssl/wildcard.ulh.cloud.cert";
    ssl_certificate_key "/root/.ssl/wildcard.ulh.cloud.key";
    ssl_session_cache shared:SSL:1m;
    ssl_session_timeout 10m;
    ssl_ciphers HIGH:!aNULL:!MD5;
    ssl_prefer_server_ciphers on;

    # Load configuration files for the default server block.
    include /etc/nginx/default.d/*.conf;

    location / {
    }

    error_page 404 /404.html;
      location = /40x.html {
    }

    error_page 500 502 503 504 /50x.html;
      location = /50x.html {
    }
  }

}

After the upgrade we have this error when accessing to https://imt.ulh.cloud

Type Exception Report
Message /ords
Description The server encountered an unexpected condition that prevented it from fulfilling the request.
Exception
java.lang.IllegalArgumentException: /ords
	oracle.dbtools.http.servlet.UriRequest.<init>(UriRequest.java:40)
	oracle.dbtools.http.servlet.UriRequest.uriRequest(UriRequest.java:453)
	oracle.dbtools.http.errors.ResponseFlusher.<init>(ResponseFlusher.java:35)
	oracle.dbtools.http.errors.ErrorPageRenderer.service(ErrorPageRenderer.java:60)
	oracle.dbtools.http.entrypoint.EntryPointServlet.service(EntryPointServlet.java:131)
	oracle.dbtools.entrypoint.WebApplicationRequestEntryPoint.service(WebApplicationRequestEntryPoint.java:50)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
	org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
Note The full stack trace of the root cause is available in the server logs.

But when accessing indicating "/ords/f?p=application_id" (https://imt.ulh.cloud/ords/f?p=500) it works perfectly.
Any clue would be very helpful.
Thanks,
Jose.