# Ignition Edge Auto Launch Project **URL:** \ **Category:** Ignition\ **Created:** [November 5, 2019, 2:07pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-auto-launch-project/29682 "2019-11-05T14:07:24Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![abishur](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/abishur/32/9096_2.png) [@abishur](https://forum.inductiveautomation.com/u/abishur)\ **Post date:** [November 5, 2019, 2:07pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-auto-launch-project/29682/1 "2019-11-05T14:07:24Z")
I was curious if there were any plans to add the ability to auto launch a project when the gateway loads in the future. Using Linux I use their startup programs and then delay the running of a script to launch the project, but I either have to over delay it or have random instances where I tried to start it just barely too soon before the gateway finished loading. Recently I’ve started getting an error message when the client tries to load the project stating “Error launching application: EOFException: null” I’m headed out to the site today to try and get some log file information on what that is occurring, however my suspicion is I ran the script too early. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [November 5, 2019, 2:11pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-auto-launch-project/29682/2 "2019-11-05T14:11:29Z")
Consider adding a startup dependency between the display manager and the Ignition service. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [November 5, 2019, 3:38pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-auto-launch-project/29682/3 "2019-11-05T15:38:27Z")
Find your `Ignition-Gateway.service` file (probably in `/etc/systemd/system/`). Edit the `[Unit]` section and add `Before=graphical.target`: ```auto [Unit] Description=Ignition-Gateway After=syslog.target Before=graphical.target ``` (untested) ---
**Author:** ![abishur](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/abishur/32/9096_2.png) [@abishur](https://forum.inductiveautomation.com/u/abishur)\ **Post date:** [November 5, 2019, 4:38pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-auto-launch-project/29682/4 "2019-11-05T16:38:57Z")
Okay, I’m using Ignition 8.0.6-rc1 that I just downloaded on Linux Mint (Ubuntu flavor). I’ve installed as a service using `sudo ./ignition.sh installstart`. I went into the Ignition-Gateway.service file and added `Before=grapical.target` to the `[Unit]` section. The service has started but no project is launched. Is there another step I need to do or do I need to go to 8.0.5 or 8.0.7? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [November 5, 2019, 4:48pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-auto-launch-project/29682/5 "2019-11-05T16:48:24Z")
This would be in addition to your script placed in startup programs - you still doing that? ---
**Author:** ![abishur](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/abishur/32/9096_2.png) [@abishur](https://forum.inductiveautomation.com/u/abishur)\ **Post date:** [November 5, 2019, 4:53pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-auto-launch-project/29682/6 "2019-11-05T16:53:54Z")
Ah, no I was not I thought that replaced the startup script. I’ve added it back in and it works like a champ, thank you! ---
**Author:** ![Cole\_Townsend](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cole_townsend/32/53149_2.png) [@Cole\_Townsend](https://forum.inductiveautomation.com/u/Cole_Townsend)\ **Post date:** [September 27, 2023, 2:02pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-auto-launch-project/29682/7 "2023-09-27T14:02:37Z")
@Kevin.Herron Having an issue with the solution here. We have set up the graphical.target with a dependency for the Ignition-Gateway.service but when we run our .desktop startup script that opens a browser with our perspective project, we are still getting a 503 service error as if the project is not available yet. Has something changed in the last 4 years where Perspective projects act differently? Is there still a delay between the service starting and project URLs being available? ---
**Author:** ![Cole\_Townsend](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cole_townsend/32/53149_2.png) [@Cole\_Townsend](https://forum.inductiveautomation.com/u/Cole_Townsend)\ **Post date:** [September 27, 2023, 2:35pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-auto-launch-project/29682/8 "2023-09-27T14:35:34Z")
Just did a test where my startup script included `systemctl status Ignition-Gateway.service` and it did show that the gateway service was running when the script ran. So that means the gateway is running but the perspective endpoint is not open yet. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [September 27, 2023, 2:51pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-auto-launch-project/29682/9 "2023-09-27T14:51:01Z")
I wouldn’t be surprised if there is some kind of delay there. I don’t think it’s intentional or not, and probably hasn’t changed intentionally or not. A script might need to be a little smarter, doing something like `curl` or `wget` in a wait-loop until the desired endpoint returns a 200 status or a threshold to give up is reached. ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [September 27, 2023, 4:02pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-auto-launch-project/29682/10 "2023-09-27T16:02:01Z")
I've never had issues with this. When the client launches, it usually just shows the splash screen showing it's trying to connect to the gateway, then once the gateway becomes available, it connects up and opens the project. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [September 27, 2023, 4:07pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-auto-launch-project/29682/11 "2023-09-27T16:07:17Z")
Sounds like you're launching a Vision client and not a browser pointing at a Perspective project URL. ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [September 27, 2023, 4:14pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-auto-launch-project/29682/12 "2023-09-27T16:14:18Z")
Ahh, I missed that part in his original message. I always use the respective client apps and never have the issue with this. ---
**Author:** ![Andrew\_Harper](https://avatars.discourse-cdn.com/v4/letter/a/a88e57/32.png) [@Andrew\_Harper](https://forum.inductiveautomation.com/u/Andrew_Harper)\ **Post date:** [November 14, 2023, 2:48pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-auto-launch-project/29682/13 "2023-11-14T14:48:02Z")
As mentioned here, we implemented curl to pull the HTTP status code and loop until the perspective project loads and the desired status code is reached. Thus far, it has worked nicely. Thanks for the tip on this.