connection problem during deployment
hello!

i see permanent connection problems during custom code deployment (via “npm run deploy”). the error message:

20:32:59.641 publishing model to server

20:37:03.572 error: unable to publish model. no connection with server

meanwhile, “npm run debug” works. app id: 7d0ca196-6bfb-3b9f-ff01-ebb4…
[@andrey-olishchuk](/u/andrey-olishchuk) the issue is fixed i was able to deploy your project
was caused because there was an "unhandled rejection error: eacces: permission denied, mkdir '/home//.npm/\_cache/index-<…>/

solved problem by just adding “sudo” in front

sudo npx create-react-app . sorry i took so long to respond on this post. i’ve had a busy week! so i found the issue. in my template for endpoints i realized i accidentally set them to provision using the external ip address of my pbx. changed it to internal and this fixed my issues :stuck\_out\_tongue: hi mike, thanks for bringing this to our attention, i can confirm that i’m aware of this issue and a fix is in progress. i expect the latest version to be available the debian/rpm repositories in the coming days.

one short term work around would be to download the .deb or .rpm file directly from th… hi, i think i was able to isolate the issue to flights dispatched via the simbrief api.

it should be fixed now, let me know if you still have the issue in future flights.

thanks, Hi everyone,
 
Sorry for the trouble and inconvenience that this issue has caused you. The issue related to publishing services is now fixed. 
Please let us know if you're still facing issues while updating or creating prototype links. 
 
Thanks,
Harshika i was able to solve this with david’s help.

the issue was on the 43763 node (the one i was trying to connect to). since i have shell access to the remote node 43763 as well, i was able to update the rpt\_extnodes file there. in non-hamvoip asl, this is performed by running the rc.updatenodelist scri… just a heads up. i believe we found the solution. as far as we could tell, these issues began to happen after we moved everything to windows 7. however, one of the helpdesk people said they thought they remembered it happening once before that while the computers were still all xp. 
i looked into the av, which was moved to a different server and upgraded shortly before our windows 7 project began. evidently, trend's migration tool that was used did not migrate over port exceptions in the firewall. after adding a few recommended exceptions to the firewall, everything started to work. 
it seems that the client firewall was blocking return snmp traffic from the printer which was keeping the computer from realizing that printing had completed. this was keeping the connection open to the printer preventing anything else from printing on that computer or any others connected to it. 
the ports added as exceptions were: udp 161(probably the only one needed), tcp 9100, 9220, 9500. Dear Jay Nelish


Your Question is incomplete


is the specific system is not on Network? its might be a problem discovered last year, that system ping but not share any data, or cannot access the system


you click on start menu and then click on run  

type serivces.msc  

and run the computer browser service, Remote Procedure call service, Server, and Client service


and your problem will resolved  

but actually this is because of virus change your antivirus program and scan your system wtih updated A/V I've found a solve that works for me! This was totally my fault, but it took me ages to figure out! Syncing for CC had paused under my preferences in the CCD app. I resumed them and everything started working again – the publishing finishes and I can share libraries etc. we believe this issue has been fixed with our most recent release, version 10.9.
 


 you can learn more here:
 



 please try updating, and let me know if you have any other questions.
 


  
 


 also, if you are experiencing this issue via the web client, please let us know here: