I've successfully used the generative tool on another machine but my current setup when hitting generate it gives me an get session ID error. Reinstalled, rebooted, same results.
On the desktop PC - in general, everything works fine. On a laptop only via VPN. Both on Windows 11. Both on the same router. Laptop via Wi-Fi. Desktop - Ethernet. Marvel 🙂
I suspect the issue does have something to do with network connections or Proxies or internet filtering somehow. I experience the session ID error on my desktop (PC) but not my laptop (Macbook). Both are on my work network. The Macbook does not appear to have any Proxy settings enabled, but my PC desktop has a Proxy script enabled. I cannot turn this off as it is managed by our organization and I cannot make changes to the settings. I also cannot test through a VPN as VPNs are blocked on our work network.
I know this feature is cloud based and requires an internet connection, so I suspect it is trying to connect to a resource on the internet that is being blocked by my network or internet filter. I wonder if Adobe can provide some addresses that can be whitelisted on our internet filter?
This is what I get when I clicker generate on the new beta photoshop generative ai feature [An error occurred during image generation: error get_session_id session id not found: 1000
Hello, the actual way to fix this on a Mac... go to System Preferences - Network - Advanced - Proxies - UNCHECK both Web Proxy (HTTP) and Secure Web Proxy (HTTPS). Now try again. Good Luck!
p.s. i don't think the adobe website, and forums in particular, are easy to navigate, so don't spend a lot of time searching that forum list. do your best and we'll move the post if it helps you get responses.
It sounds like disbaling the proxy seems to work for those who can do that. In my case, I have no control over the proxy. It is configured by my organization for our internet content filter and it cannot be disabled. If it is something that is being blocked by our filter, it would be beneficial to know exactly where the traffic is tryng to go that is being blocked so that out netwrok administrator can whitelist or unblock it.
For my environment our web filter was preventing the session connection. Whitlisting it alone did not fix it. We had to add sensei-ue1.adobe.io to our SSL decryption exclusion list in order to get it to work.
@MichaelG-IS , that was it! Our network admnistrator added sensei-ue1.adobe.io to our SSL decryption exclusion list and it finally works for me - no session ID error. Thank you for posting the fix!
Thanks for the tip Cory, I tried (on a Windows machine) holding Shift+Alt+Ctrl and then opening the app again after closing it. That seemed to clear the issue for me.