What is the issue or question you have?
Hello, I’m from Iran and I use VPN for run the models of INVEST, now for this Model I have this error “cannot connect to (‘34.44.144.58’, 54322): [WinError 10060]”.
pls help me to solve it.
thank you
Hello, I’m from Iran and I use VPN for run the models of INVEST, now for this Model I have this error “cannot connect to (‘34.44.144.58’, 54322): [WinError 10060]”.
pls help me to solve it.
thank you
Hi @ziba76,
The Rec model server seems to be in working order and I can successfully run the model on the sample data. In general, this sort of error tends to happen when your internet connection isn’t stable. If you’re still experiencing this problem, could you please upload your logfile? That would help me pin down the exact problem.
Thanks!
Hello, and thank you very much for your prompt response and support.
As requested, I’m sharing two log reports from running the Recreation model. The first run was executed with a VPN connection, and the second one without VPN. Both runs resulted in errors related to server access or URI configuration.
Run with VPN:
Code
09/18/2025 17:21:52 natcap.invest.utils Level 100 Writing log messages to [D:\Master\py\Invest\recration\InVEST-recreation-log-2025-09-18--17_21_52.txt]
09/18/2025 17:21:52 __main__ Level 100 Starting model with parameters:
Arguments for InVEST recreation 3.16.2:
aoi_path C:\Users\negin\Desktop\Khuzestan wetlands\all.shp
cell_size
compute_regression False
end_year 2017
grid_aoi False
grid_type square
n_workers -1
predictor_table_path
results_suffix
scenario_predictor_table_path
start_year 2015
workspace_dir D:\Master\py\Invest\recration
09/18/2025 17:21:53 natcap.invest.recreation.recmodel_client INFO PYRO:natcap.invest.recreation@34.44.144.58:54322
09/18/2025 17:21:53 natcap.invest.recreation.recmodel_client INFO Contacting server, please wait.
09/18/2025 17:22:16 taskgraph.Task ERROR Something went wrong when adding task user-day-calculation (1), terminating taskgraph.
Pyro5.errors.CommunicationError: cannot connect to ('34.44.144.58', 54322): [WinError 10060] A connection attempt failed because the connected party did not properly respond...
09/18/2025 17:22:16 natcap.invest.utils INFO Elapsed time: 24.11s
09/18/2025 17:22:16 natcap.invest.utils INFO Execution finished; version: 3.16.2
Run without VPN:
Code
09/18/2025 17:19:03 natcap.invest.utils Level 100 Writing log messages to [D:\Master\py\Invest\recration\InVEST-recreation-log-2025-09-18--17_19_03.txt]
09/18/2025 17:19:03 __main__ Level 100 Starting model with parameters:
Arguments for InVEST recreation 3.16.2:
aoi_path C:\Users\negin\Desktop\Khuzestan wetlands\all.shp
...
09/18/2025 17:19:03 natcap.invest.recreation.recmodel_client INFO <?xml version='1.0' encoding='UTF-8'?><Error><Code>AccessDenied</Code><Message>Access denied.</Message></Error>
09/18/2025 17:19:04 natcap.invest.recreation.recmodel_client INFO Contacting server, please wait.
09/18/2025 17:19:04 taskgraph.Task ERROR Something went wrong when adding task user-day-calculation (1), terminating taskgraph.
Pyro5.errors.PyroError: invalid uri
09/18/2025 17:19:04 natcap.invest.utils INFO Elapsed time: 0.85s
09/18/2025 17:19:04 natcap.invest.utils INFO Execution finished; version: 3.16.2
I’ve attached both log files for your review. Please let me know if there’s anything else I can provide to help diagnose the issue.
Best regards, Ziba
HI @ziba76 , thanks for sharing your logs. This model, unlike other invest models, requires a connection to a remote server on Google Cloud. The non-VPN log shows a failure to retrieve the server’s URL from a lookup we keep on Google Cloud. So the VPN allows you to access that google cloud resource and get the correct URL for the server, but you still can’t connect to that server.
I believe in this case the “connected party” is your computer. The server is trying to establish a connection with your computer by using a “handshake”, and it seems like your computer may not be allowing the incoming message from the server. That could be due to firewall rules, or VPN settings, or something else having to do with your network. It is a difficult problem to diagnose. If you are able to figure something out, please do let us know.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.