Forum

1C Mobile Client Server Error

Bahrom	#1 Sep 28, 2025 10:14 PM
Active user Points:: 0 Joined:: Apr 2, 2025	Mobile Phone: Samsung Galaxy Note 10+, Android system 1C Mobile Client version: 8.3.25.60 I am successfully connecting to the Web Server, then signing in successfully. When I try to open Catalog "Product" or other objects I am getting an error in the attached image file.
	Profile

Bahrom	#2 Sep 29, 2025 03:03 PM
Active user Points:: 0 Joined:: Apr 2, 2025	On web browser (Chrome), however, no such error, everything is fine.
	Profile

Aleksandr Biryukov	#3 Sep 30, 2025 10:32 AM
Administrator Points:: 0 Joined:: Oct 3, 2019	Hello Bahrom, clarify please which 1C configuration you are using?
	Profile

Bahrom	#4 Sep 30, 2025 03:27 PM
Active user Points:: 0 Joined:: Apr 2, 2025	New configuration, with SSL merged. 1C:Enterprise 8.3 (8.3.24.1819) SSL: 3.1.10.386
	Profile

Bahrom

Oct 03, 2025 04:53 AM

Active user

Points:: 0
Joined:: Apr 2, 2025

I added following into web.config file

Code
<system.web> <customErrors mode="Off"/> </system.web>

Now the error says "A potentially dangerous Request.Path value was detected from the client ( : )".

In browser I see this error when I open a report.

In 1C Mobile Client (version: 8.3.25.60) On all objects while opening them.

Profile

Aleksandr Biryukov	#6 Oct 09, 2025 08:32 PM
Administrator Points:: 0 Joined:: Oct 3, 2019	Hello Bahrom, also, please clarify—are you using the "1C Mobile Client"? It's worth noting that the mobile platform comes with a variety of files, but we specifically need the mobile client file (see screenshot). This may be the reason for the error... Also describe how you published the program on the web server? "Administration" -> "Publish to web server"?
	Profile

Bahrom	#7 Oct 10, 2025 09:47 AM
Active user Points:: 0 Joined:: Apr 2, 2025	Please, see the device info in the attached file. ChatGPT says "Your phone’s Exynos 9825 is a 64-bit ARM processor — specifically based on the ARMv8-A architecture.". That is the reason I installed 1cem-client-arm64.apk. See the attached files how I am publishing the conf. After publishing I am restarting the Web Server. But the error still persists.
	Profile

Bahrom	#8 Oct 10, 2025 10:32 AM
Active user Points:: 0 Joined:: Apr 2, 2025	I installed 1cem-client-arm64.apk
	Profile

Aleksandr Biryukov	#9 Oct 12, 2025 02:56 PM
Administrator Points:: 0 Joined:: Oct 3, 2019	OK. Then let's try the following: Try running the mobile client on a clean 1C database, without using SLL.
	Profile

Bahrom	#10 Oct 12, 2025 07:18 PM
Active user Points:: 0 Joined:: Apr 2, 2025	I tested a new database without SSL. The error persists!
	Profile

Aleksandr Biryukov	#11 Oct 14, 2025 11:30 PM
Administrator Points:: 0 Joined:: Oct 3, 2019	Hello! What web server are you using? Also, could you install 1C mobile client on another device and try it there?
	Profile

Bahrom

#12

Oct 15, 2025 01:19 PM

Active user

Points:: 0
Joined:: Apr 2, 2025

My Web Server is Internet Information Services, aka IIS.

Quote
could you install 1C mobile client on another device and try it there?

I am getting this error not only on my mobile phone but also on the computer where I installed the 1C Server and on other several computers. See the screenshot.

Profile

Bahrom	#13 Oct 15, 2025 01:32 PM
Active user Points:: 0 Joined:: Apr 2, 2025	I asked ChatGPT about this error. See in the attached files its answer.
	Profile

Bahrom	#14 Oct 15, 2025 01:33 PM
Active user Points:: 0 Joined:: Apr 2, 2025	And the last file
	Profile

Aleksandr Biryukov

#15

Oct 20, 2025 02:41 PM

Administrator

Points:: 0
Joined:: Oct 3, 2019

Quote
Bahrom wrote: I am getting this error not only on my mobile phone but also on the computer where I installed the 1C Server and on other several computers. See the screenshot.

Hello!

You previously mentioned that the error occurs only when working from a mobile device, and that it does not appear when accessing the database through a browser.

Now you’re saying that the error also occurs when using the browser — is that correct?

The reason this is important for me to know is that it will help me understand where to look for the issue — whether it’s in the web server configuration, the mobile client, or somewhere else.

Profile

Aleksandr Biryukov	#16 Oct 20, 2025 05:40 PM
Administrator Points:: 0 Joined:: Oct 3, 2019	Hello Bahrom, I believe the issue is related to the web server settings... Please try performing the actions shown in the screenshot.
	Profile

Bahrom	#17 Oct 20, 2025 08:29 PM
Active user Points:: 0 Joined:: Apr 2, 2025	Nice job!!! Thumbs up!!! Problem solved!!!
	Profile

Aleksandr Biryukov	#18 Oct 21, 2025 10:51 AM
Administrator Points:: 0 Joined:: Oct 3, 2019	Excellent!
	Profile