No Matches Found!
Try with a different search term
No Matches Found!
Try with a different search term
There's a new home for Articles. Find Articles on Our Product Support Page.
We're starting with soti connect (cloud) and planning to add Zebra printers by MQTT. The networkteam wanted the exact ports which we're using. We're thinking about 433 (https) 8883 (MQTTS) 4646/4650 (filestore) wich are inbound, outbound or both?
Hello everyone, Since the last Soti Connect update (2024.2.0.8055) the automapping no longer works automatically.The "rule" itself works, if you open the rule under (Administration->Automatic Group Mappings) and click on save, the devices are moved immediately correctly.I created the rule based on a specific IP range A short explanation of how I built the rules: Device is staged, after enrollment the device is moved to a superordinate group (Devices all Companies). And from this group, the device should be moved to the respective company based on the IP range (automapping) Any ideas? Or known problems? Thanks Greetings Max
I'm trying to access the Soti Connect API on our cloud-hosted instance using the Resource Owner grant type as documented at Soti Connect Help: Request Access Token. Here are the steps I've taken: Add a new client ID and secret as documented at Global Settings: General --> Security Access Add a new local Soti Connect user specifically for API access Send a request to https://hostname/Connect/token I receive an error message that the password must be changed. error error_description----- -----------------access_denied {"errorCode":161,"parameter":"IsPasswordChangeRequired"} The problem is that we're using Soti Identity for authentication, and disabling that just to change a password seems excessive. I realize this may be an example of an XY problem, so if there's a better way to do this than to create a local user, I'm interested.
Hi. I am currently trying to connect to our CA from Soti Connect. But we are running into an error. If I run the proxy test under "Services > Global Proxy" with the URL of the CA, then it works. We can also see this connection on the proxy. [DEBUG] [58] [Soti.IoT.ManagementServer.exe] Send Request to http://CA-SERVER/TEMPLATENAME via proxy service $PROXYSERVER:8080[DEBUG] [59] [Soti.IoT.ManagementServer.exe] Test proxy service connection: Success. However, if I then want to create a certificate or simply press the test-connection button at "Administration > Device Certificates and Templates”, we run into an error. Here we see no connection to the CA on the proxy. [ERROR] [46] [Soti.IoT.ManagementServer.exe] Fail to connect to CA server with CA template:TEMPLATENAME Any idea where the problem might lie? Important: For security reasons, the Soti Connect Server has no connection to the Internet. Best regardsHauke
Hi, I'm trying to enroll a TSC MH241T printer into Connect.Broker and MQTT are already installed. Ports are open and reachable but for some reason I can't enroll that printer.Rules are also configured in Connect. The only thing where I'm missing some information is on the printer itself.When I logon to the printer, through the webportal I need to fill in some data but not sure what to fill in. MQTT Server: xxxx.soticonnect.cloud ?MQTT Server Port : 8883MQTT Username: can be found in the zpl fileMQTT Password: can be found in the zpl fileMQTT Secured: Should be TLSMQTT CA: ?? where to find that one (need to be uploaded to the printer? small part from the zpl file?)MQTT Client Cert: ???MQTT Private Key: ???Private Key Password: ???File Store CA: Root cert from Connect?Soti Tenant ID: where can I find that
Top-tier experts who are delivering outstanding content. Should have more than 7000 points.
Experts who are consistent with great content. Should have more than 1000 points.
Highly experienced members with valuable inputs. Should have more than 700 points.
Beginners taking the initiative. Should have more than 500 points.
New contributors starting their journey. Should have more than 250 points.
