This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 63%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAR%3C/text%3E%3C/svg%3E)
Hi there,
Following this link:
I have reproduced the exact configuration for the docker-compose file and also for all requisites necessary to run the Custom container, version 3.0.
The containers (layout, custom-template and studio) start normally, but when I access the Form Recognizer Studio and try to train a new model, I am getting the following error:
Cannot read properties of undefined (reading 'status').
Any help or tip to get this solved will be welcome. Thank you.
Just adding a new information about the error. From the browser console I got the following message/error:
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(195.2, 4%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVM%3C/text%3E%3C/svg%3E)
Hi @Adeilson Rocha Brito , Thanks for sharing these details with us.
Please allow some time to check internally and will get back to you on this.
Thank you so much for your attention and support.
Hi @Adeilson Rocha Brito , it looks like error when creating custom model project, can you please check the write permission to the DB_MOUNT_PATH?
The issue may also be caused by the network setting such as nginx. Is it possible to share your configuration files (.env, nginx.conf, and docker-compose.yml) with us for further investigation?
Please send these files to azcommunity@microsoft.com with the below details, so that we can work closely on this matter.
Thread URL: Link to this thread.
Your Azure Subscription ID:
Email Subject : Attn Vasavi
Configuration files:
Yes, for sure. I will send the requested files.
Regarding the env variable DB_MOUNT_PATH, I have applied "chmod 777" to the folder before, but the error remains. You can see in the image below that I have granted 777 for all folders as an attempt to solve this issue.
Thank you.
Hi @Adeilson Rocha Brito , thanks for sharing the files. Will check and let you know.
Hi @Adeilson Rocha Brito , Thank you for your patience.
The configuration files provided by you was able to successfully run the container, create project, and train on our end. Since the error is related to connection refused, and if the container is started normally, one possibility may be the firewall setting or something blocking the connection in your machine.
Is it possible to check for network trace on browser and also share the container logs?
Hi @VasaviLankipalle-MSFT sorry for the delay (was off yesterday).
For sure. Let me collect a trace and I will share with you.
Hi @VasaviLankipalle-MSFT,
Initially I did trace my perimeter firewall and created a rule to allow any connection from/to the server that is running the compose. That means no blocking with external requisitions.
At the same time I inactivated the server firewall (this an Ubuntu server, then just put the ufw as inactive), and also did a trace regarding the server firewall.
Monitoring both traffic I did not see any block between the server and external services (Azure) and either internal. However, the same error remains.
Additionally, I also instantiated the containers using the root user, even though all folders are granted with chmod 777. The error remains.
A question or possibility I wanted to check out with you: I am using the docker version as below. Is there any requisite to use a most recent version to run the form recognizer containers?
I am sending by email the log file for your assessment.
Thank you so much for your support so far. Really appreciate it.
Best.
Hope you are doing well. Just wanted let you know that I sent an email with new details about this issue.
I realized that the Form Recognizer is working perfectly when I make a remote access to the host machine and open the Form Recognizer Studio directly on the web browser of that host machine.
However, if I access the Form Recognizer Studio using the browser in a different machine, being necessary, in that case, to provide the IP address of the Form Recognizer host, I face the error that we have been discussing so far.
Thank you for your patience and support.
After pull the new Docker image versions the solution is now working correctly.