OpenVidu Server does not have path /inspector/accept-certificate mapped in new version

I installed the new version 2.13 and it gives me the following error:

ERROR: unknown URL https://frikivideo.cecotec.es/inspector/accept-certificate
OpenVidu Server does not have path /inspector/accept-certificate mapped
If you are seeing this message as a result of COMPOSED recording, the problem is most likely an issue with the recording URL.
Current recording URL is https://frikivideo.cecotec.es/inspector/accept-certificate
The recording service cannot access the recording layout through this URL.
Use OpenVidu configuration property OPENVIDU_RECORDING_COMPOSED_URL to provide a valid URL for the recording service to connect to.

attached the .env info:

> # OpenVidu configuration
> 
> # ----------------------
> 
> # Documentation: https://docs.openvidu.io/en/stable/reference-docs/openvidu-config/
> 
> # NOTE: This file doesn’t need to quote assignment values, like most shells do.
> 
> # All values are stored as-is, even if they contain spaces, so don’t quote them.
> 
> # Domain name. If you do not have one, the public IP of the machine.
> 
> # For example: 198.51.100.1, or [openvidu.example.com](http://openvidu.example.com/)
> 
> OPENVIDU_DOMAIN_OR_PUBLIC_IP=frikivideo.cecotec.es
> 
> # OpenVidu PRO License
> 
> OPENVIDU_PRO_LICENSE=98b439f6-010e-xxxx-b3eb-xxxxxxxxxx
> 
> # OpenVidu SECRET used for apps to connect to OpenVidu server and users to access to OpenVidu Dashboard
> 
> OPENVIDU_SECRET=xxxxxx
> 
> # Certificate type:
> 
> # - selfsigned: Self signed certificate. Not recommended for production use.
> 
> # Users will see an ERROR when connected to web page.
> 
> # - owncert: Valid certificate purchased in a Internet services company.
> 
> # Please put the certificates files inside folder ./owncert
> 
> # with names certificate.key and certificate.cert
> 
> # - letsencrypt: Generate a new certificate using letsencrypt. Please set the
> 
> # required contact email for Let’s Encrypt in LETSENCRYPT_EMAIL
> 
> # variable.
> 
> CERTIFICATE_TYPE=letsencrypt
> 
> # If CERTIFICATE_TYPE=letsencrypt, you need to configure a valid email for notifications
> 
> LETSENCRYPT_EMAIL=xxxxx
> 
> # Mode of cluster management. Can be auto (OpenVidu manages Media Nodes on its own.
> 
> # Parameter KMS_URIS is ignored) or manual (user must manage Media Nodes. Parameter
> 
> # KMS_URIS is used: if any uri is provided it must be valid)
> 
> OPENVIDU_PRO_CLUSTER_MODE=auto
> 
> # Which environment are you using
> 
> # Possibles values: aws, on_premise
> 
> OPENVIDU_PRO_CLUSTER_ENVIRONMENT=aws
> 
> # The desired number of Media Nodes on startup. First the autodiscovery process is performed.
> 
> # If there are too many Media Nodes after that, they will be dropped until this number is reached.
> 
> # If there are not enough, more will be launched.
> 
> # This only takes place if OPENVIDU_PRO_CLUSTER_MODE is set to auto
> 
> # If set to zero no media servers will be lauched.
> 
> # Type: number >= 0
> 
> OPENVIDU_PRO_CLUSTER_MEDIA_NODES=3
> 
> # What parameter should be used to distribute the creation of new sessions
> 
> # (and therefore distribution of load) among all available Media Nodes
> 
> OPENVIDU_PRO_CLUSTER_LOAD_STRATEGY=streams
> 
> # Whether to enable recording module or not
> 
> OPENVIDU_RECORDING=false
> 
> # Openvidu Folder Record used for save the openvidu recording videos. Change it
> 
> # with the folder you want to use from your host.
> 
> OPENVIDU_RECORDING_PATH=/opt/openvidu/recordings
> 
> # System path where OpenVidu Server should look for custom recording layouts
> 
> OPENVIDU_RECORDING_CUSTOM_LAYOUT=/opt/openvidu/custom-layout
> 
> # if true any client can connect to
> 
> # https://OPENVIDU_SERVER_IP:OPENVIDU_PORT/recordings/any_session_file.mp4
> 
> # and access any recorded video file. If false this path will be secured with
> 
> # OPENVIDU_SECRET param just as OpenVidu Server dashboard at
> 
> # https://OPENVIDU_SERVER_IP:OPENVIDU_PORT
> 
> # Values: true | false
> 
> OPENVIDU_RECORDING_PUBLIC_ACCESS=false
> 
> # Which users should receive the recording events in the client side
> 
> # (recordingStarted, recordingStopped). Can be all (every user connected to
> 
> # the session), publisher_moderator (users with role ‘PUBLISHER’ or
> 
> # ‘MODERATOR’), moderator (only users with role ‘MODERATOR’) or none
> 
> # (no user will receive these events)
> 
> OPENVIDU_RECORDING_NOTIFICATION=publisher_moderator
> 
> # Timeout in seconds for recordings to automatically stop (and the session involved to be closed)
> 
> # when conditions are met: a session recording is started but no user is publishing to it or a session
> 
> # is being recorded and last user disconnects. If a user publishes within the timeout in either case,
> 
> # the automatic stop of the recording is cancelled
> 
> # 0 means no timeout
> 
> OPENVIDU_RECORDING_AUTOSTOP_TIMEOUT=120
> 
> # Maximum video bandwidth sent from clients to OpenVidu Server, in kbps.
> 
> # 0 means unconstrained
> 
> OPENVIDU_STREAMS_VIDEO_MAX_RECV_BANDWIDTH=1000
> 
> # Minimum video bandwidth sent from clients to OpenVidu Server, in kbps.
> 
> # 0 means unconstrained
> 
> OPENVIDU_STREAMS_VIDEO_MIN_RECV_BANDWIDTH=300
> 
> # Maximum video bandwidth sent from OpenVidu Server to clients, in kbps.
> 
> # 0 means unconstrained
> 
> OPENVIDU_STREAMS_VIDEO_MAX_SEND_BANDWIDTH=1000
> 
> # Minimum video bandwidth sent from OpenVidu Server to clients, in kbps.
> 
> # 0 means unconstrained
> 
> OPENVIDU_STREAMS_VIDEO_MIN_SEND_BANDWIDTH=300
> 
> # true to enable OpenVidu Webhook service. false’ otherwise
> 
> # Values: true | false
> 
> OPENVIDU_WEBHOOK=false
> 
> # HTTP endpoint where OpenVidu Server will send Webhook HTTP POST messages
> 
> # Must be a valid URL: http(s)://ENDPOINT
> 
> #OPENVIDU_WEBHOOK_ENDPOINT=
> 
> # List of headers that OpenVidu Webhook service will attach to HTTP POST messages
> 
> #OPENVIDU_WEBHOOK_HEADERS=
> 
> # List of events that will be sent by OpenVidu Webhook service
> 
> # Leave blank if all events.
> 
> OPENVIDU_WEBHOOK_EVENTS=[sessionCreated,sessionDestroyed,participantJoined,participantLeft,webrtcConnectionCreated,webrtcConnectionDestroyed,recordingStatusChanged,filterEventDispatched,mediaNodeStatusChanged]
> 
> # How often the garbage collector of non active sessions runs.
> 
> # This helps cleaning up sessions that have been initialized through
> 
> # REST API (and maybe tokens have been created for them) but have had no users connected.
> 
> # Default to 900s (15 mins). 0 to disable non active sessions garbage collector
> 
> OPENVIDU_SESSIONS_GARBAGE_INTERVAL=900
> 
> # Minimum time in seconds that a non active session must have been in existence
> 
> # for the garbage collector of non active sessions to remove it. Default to 3600s (1 hour).
> 
> # If non active sessions garbage collector is disabled
> 
> # (property ‘OPENVIDU_SESSIONS_GARBAGE_INTERVAL’ to 0) this property is ignored
> 
> OPENVIDU_SESSIONS_GARBAGE_THRESHOLD=3600
> 
> # Call Detail Record enabled
> 
> # Whether to enable Call Detail Record or not
> 
> # Values: true | false
> 
> OPENVIDU_CDR=false
> 
> # Path where the cdr log files are hosted
> 
> OPENVIDU_CDR_PATH=/opt/openvidu/cdr
> 
> # Kurento Media Server image
> 
> # --------------------------
> 
> # Docker hub kurento media server: https://hub.docker.com/r/kurento/kurento-media-server-dev
> 
> # Uncomment the next line and define this variable with KMS image that you want use
> 
> # KMS_IMAGE=kurento/kurento-media-server-dev:6.13
> 
> # Kurento Media Server Level logs
> 
> # -------------------------------
> 
> # Uncomment the next line and define this variable to change
> 
> # the verbosity level of the logs of KMS
> 
> # Documentation: https://doc-kurento.readthedocs.io/en/stable/features/logging.html
> 
> # KMS_DEBUG_LEVEL=3,Kurento*:4,kms*:4,sdp*:4,webrtc*:4, *rtpendpoint:4,rtp* handler:4,rtpsynchronizer:4,agnosticbin:4
> 
> # Openvidu Server Level logs
> 
> # --------------------------
> 
> # Uncomment the next line and define this variable to change
> 
> # the verbosity level of the logs of Openvidu Service
> 
> # RECOMENDED VALUES: INFO for normal logs DEBUG for more verbose logs
> 
> # OV_CE_DEBUG_LEVEL=INFO
> 
> # Java Options
> 
> # --------------------------
> 
> # Uncomment the next line and define this to add options to java command
> 
> # Documentation: https://docs.oracle.com/cd/E37116_01/install.111210/e23737/configuring_jvm.htm#OUDIG00058
> 
> # JAVA_OPTIONS=-Xms2048m -Xmx4096m
> 
> # Kibana And ElasticSearch Configuration
> 
> # --------------------------
> 
> # Kibana dashboard configuration (Credentials)
> 
> KIBANA_USER=xxxx
> KIBANA_PASSWORD=xxxx
> 
> # Cloudformation configuration
> 
> # --------------------------
> 
> # If you’re working outside AWS ignore this section
> 
> AWS_DEFAULT_REGION=eu-west-2
> AWS_IMAGE_ID=ami-0d06b4674583e265a
> AWS_INSTANCE_TYPE=c5.xlarge
> AWS_KEY_NAME=dani-londres
> AWS_SUBNET_ID=subnet-07b1727d
> AWS_SECURITY_GROUP=sg-0ca770ee68061cc09
> AWS_STACK_ID=arn:aws:cloudformation:eu-west-2:952964753381:stack/frikivideo/a57081b0-8870-11ea-9f96-02317fefc7aa
> AWS_STACK_NAME=xxxxx

Hello @Daniel_Cano,

Where error is shown? In OpenVidu log? When you try to connect some client? In a recording?

Are you trying to install OpenVidu CE or OpenVidu PRO? On AWS using Cloud Formation or using the installation script?

When do you get that error?

the error shows when the client is connected, if I point to version 2.12 it works fine, if I point to version 2.13 it shows me that error, use OpenVidu PRO, I use AWS Cloud Formation in both cases

Still don’t know where you get the error. Now I know when you get the error, but I need to know where:

  • OpenVidu Logs?
  • Browser console logs?
  • Recorded video?

I get the error when I point to the openvidu server, in the server log I don’t see anything because I think it doesn’t arrive, in the browser I get the following

Please show us browser console.

Error 404 is:

{“timestamp”:“2020-04-29T12:27:12.516+0000”,“status”:404,“error”:“Not Found”,“message”:“No message available”,“path”:"/inspector/api/sessions"}```


The url api firs conections: https://frikivideo.cecotec.es/inspector/api/sessions

    ERROR: unknown URL https://frikivideo.cecotec.es/inspector/api/sessions
OpenVidu Server does not have path /inspector/api/sessions mapped
If you are seeing this message as a result of COMPOSED recording, the problem is most likely an issue with the recording URL.
Current recording URL is https://frikivideo.cecotec.es/inspector/api/sessions
The recording service cannot access the recording layout through this URL.
Use OpenVidu configuration property OPENVIDU_RECORDING_COMPOSED_URL to provide a valid URL for the recording service to connect to.

I think the error message is obviously clear:

OpenVidu Server does not have path /inspector/api/sessions mapped
This means that OpenVidu Server does not have path /inspector/api/sessions

Try with /api/sessions instead

Hello,

The two URLs have been tested and neither works, but with version 2.12 of your app works without any problem, but with the new version 2.13 it does not work.

Testing your url I’m able to connect to:

  1. OpenVidu Dashboard, where you can see your OpenVidu deployment info (https://frikivideo.cecotec.es/dashboard)

  2. OpenVidu Call (https://frikivideo.cecotec.es)

  3. OpenVidu Inspector (https://frikivideo.cecotec.es/inspector)

  4. OpenVidu Server and REST API (https://frikivideo.cecotec.es)

The deployments looks like to work fine …