No Render server at address 127.0.01 problem Tweet

[dinopower]

For Octane for Blender. This was working fine, but now when I try to render an object I'm now getting a message that says: Not connected (also Server Error). No Render-server at address 127.0.01

Octane Server address says 127.0.01. When I click Activation state nothing happens.
On the Otoy website it says: Before the very first rendering you should fill in the server address.
How should I do this? It shows that its filled with 127.0.01

Octane GPU's shows my graphics card there with GeForce GTX 960m there.
The Materials Library shows up without any problems.
This could be caused by the new GeForce driver update


Operating System: Windows 10 Home 64 bit
Graphics Card: GTX 960M
RAM: 16 GB
Nvidia driver version: GeForce driver 376.19 released 12-4-16
Octane for Blender 3.04.5 version 11.15

[mib2berlin]

Hi, this is may related to viewtopic.php?f=32&t=57912
Server stop working after 30-60 seconds on my system.
Sometimes I can render one scene but than get 127.0.01 problem.

Cheers, mib

[JimStar]

Thanks guys for report, I'll check it.

[einarmartinsen]

Hello.

I'm getting the same issue : not connected | no render-server at address "127.0.0.1

Please look into why this is happening as it's completely stopping me from doing a job

[einarmartinsen]

adding to my last post here:

I active the server license and while I try to render in blender, the server license window shuts down and the license is no longer active. It's like whenever I try to render in blender it kills the license.. It was working perfectly fine for a day and all of a sudden, this server error started happening. I didn't do anything special prior to this happening... I've tried to restart, update nvidia driver, reinstalled the server but I still get the same error... : error in render-server at address "127.0.0.1"

[protovu]

Maybe helpful: The last time I went through this, being totally stuck with the same message, I uninstalled both the Server and the BlenderOctane - and reinstalled. But, maybe most important, I downloaded and installed the latest Nvidia driver.
Hope you find a solution soon.

[einarmartinsen]

Thanks for the suggestion!

I did all those three steps and still got the error.
After troubleshooting a bit, it seems like the scene I had possibly ran out of GPU ram and forcefully killed the license server.. if that makes sense?
I was using fur and fog at the same time which I guess eats a lot of memory. I hoped the 2080rtx 12gb would handle more then what I experienced.

Let me know if there are any similar experiences with RAM issues and license failing

[protovu]

This does sort of remind me of another jam I was in.

The fix was:
start a new file
append all elements from the old file

If you want to get really granular, you could check render capability one element at a time.