File Path Access from Linux Server in Script Console

Ignition
1

Hello,

I have Ignition installed on a Linux server and I am accessing it from an external Windows AWS Workspace. Currently, I am unable to read file paths from the Linux server within the Script Console.

Could you please provide guidance on how to correctly access files on the Linux server in this setup? Any suggestions or configurations needed would be greatly appreciated.

example of filepath = "/home/user/documents/my_file.txt"
And Ignition version is 8.1

Thank you for your support.

2

Scripting in the Designer script console runs on the machine that is running the Designer.

You would need to execute your script somewhere that runs in the Gateway scope, like a tag event script, or by sending to a message handler.

3

If you install my Integration Toolkit, you can use the @system.util.runInGateway decorator in your project library scripts, so that calls from the designer will actually execute in the gateway.

1 Like
4

Thank you for your guidance. I’ve tried running the script in a Gateway event, but I’m still seeing the error “Files Not in path” in the logs. Here’s the script I used:

import os
import sys

path = r"/FolderName/2025-10-27"
logger = system.util.getLogger("FileCheck")
try:
    if os.path.exists(path):
        files = os.listdir(path)
        logger.info("Files in path:")
    else:
        logger.info("Files Not in path:")
except:
    exc_type, exc_obj, tb = sys.exc_info()
    lineno = tb.tb_lineno
    errormessage = "Error: " + str(lineno)+ '  ' + str(exc_obj)
    print(errormessage)

Could you please advise on why the Gateway isn’t detecting the files on the Linux server?

5

Usually, this is a permissions issue.

6

I have noticed that one of the paths appears to have full read access (drwxrwxrwx), but I’m still unable to read the directory. Since Ignition is running from outside of the Linux environment, I believe the Ignition user should not be the local user - unless I’m mistaken.

Do you have any other suggestions or insights on why the Gateway might not be able to access the path?

Thank you for your continued support.

7

Modern high-security Linux can enforce protections via labeling under SELinux ("Security Enhanced"), which can make unreadable what looks like a world-readable location.

You will need to investigate via CLI access to the server, or ask your IT for help (or whomever set up that server).