Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
federicoprato
New Contributor II

DNS restore is in progress. Please try again later.

Hello,

i am running Forticlient 7.4.3 on Ubuntu. Sometimes my client works, then when i shut down my laptop and turn it back on i keep getting this error. No restart can help in any ways. Some time passes (it generally feels random: sometimes it's like 5 mins, sometimes more than one hour passes by and the problem persists.

Then suddenly i manage to log in my vpn again...

Any suggestions on what to do?

I have this script that i run often after i restart my computer: this helps me out altering my connections and enabling the DNS again, because it seems the forticlient enters some DNS in my wifi connections, so i need to remove these entries:

#!/bin/bash

# List current running connections and allow user to select one using fzf
connection_drop_name=$(nmcli c show --active | awk 'NR>1 {print $1}' | fzf --prompt="Select a connection to drop: ")

# Check if a connection was selected
if [ -z "$connection_drop_name" ]; then
  echo "No connection selected. Exiting."
 # exit 1
fi

# Bring down the selected connection
nmcli c down "$connection_drop_name"

# List current running connections and allow user to select one using fzf
connection_name=$(nmcli c show --active | awk 'NR>1 {print $1}' | fzf --prompt="Select a connection to RESET: ")

# Check if a connection was selected
if [ -z "$connection_name" ]; then
  echo "No connection selected. Exiting."
  exit 1
fi

# Modify the connection to reset DNS settings
nmcli c modify "$connection_name" ipv6.dns ""
nmcli c modify "$connection_name" ipv4.dns ""
nmcli c modify "$connection_name" ipv6.dns-search ""
nmcli c modify "$connection_name" ipv4.dns-search ""
nmcli c modify "$connection_name" ipv4.ignore-auto-dns "no"
nmcli c modify "$connection_name" ipv6.ignore-auto-dns "no"
nmcli c modify "$connection_name" ipv4.ignore-auto-routes "no"
nmcli c modify "$connection_name" ipv6.ignore-auto-routes "no"
nmcli c modify "$connection_name" ipv4.routes ""
nmcli c modify "$connection_name" ipv6.routes ""



# Restart the network manager to apply changes
sudo systemctl restart NetworkManager
sudo systemd-resolve --flush-caches




6 REPLIES 6
Anthony_E
Staff
Staff

Hello,


Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.


Thanks,

Anthony
Network Lab engineer.
Anthony_E
Staff
Staff

Hello,

 

We are still looking for someone to help you.

We will come back to you ASAP.


Thanks,

Anthony
Network Lab engineer.
Anthony_E
Staff
Staff

Hello Federico,

 

 

The "DNS restore is in progress. Please try again later." error indicates that a DNS restoration process is currently underway, and the system is temporarily unable to process DNS-related requests. Here are steps you can take:

  1. Wait for Completion: Allow some time for the DNS restoration process to complete. This process may take a few minutes to several hours, depending on the system and the extent of the restoration.
  2. Check Status: If available, check the status of the DNS restoration process through your system's management interface or dashboard to get an estimated time for completion.
  3. Contact Support: If the issue persists beyond a reasonable time frame, contact your system administrator or Fortinet support for further assistance and to ensure there are no underlying issues causing delays.
  4. Review Logs: If you have access, review system logs for any additional error messages or warnings that might provide more context on the issue.
  5. Retry Later: Once the restoration process is complete, retry your DNS-related operations to see if the issue is resolved.
Anthony
Network Lab engineer.
federicoprato
New Contributor II

Hello and thank you for your reply. 

Do you know what is the process name in Ubuntu? I have been flushing the dns caches and i never heard about a DNS restoration process... i can browse the internet without any problems and the DNS is definitely needed there, why can't the forticlient work?

Time helps, so suddenly, sometimes after a few minutes, sometimes after some hours, the vpn starts working just fine. 

Can i export the logs and send them to you the next time this happens?

Anthony_E
Staff
Staff

Ciao Federico,

 

Let me have a look :)

Anthony
Network Lab engineer.
federicoprato
New Contributor II

Hi again!
it just happened once more. Here are some bits out of the logs that might interest you: 

 

 

==> ./confighandler.log <==
20251001 16:23:05.869 TZ=+0300 [confighandler:EROR] decorators:52 Failed to send message to fortitray: runtime directory not found
20251001 16:23:08.878 TZ=+0300 [confighandler:INFO] main:86 Received signal: SIGTERM
20251001 16:23:08.878 TZ=+0300 [confighandler:INFO] main:68 Webserver shutting down
20251002 10:00:41.092 TZ=+0300 [confighandler:EROR] auth:30 Failed to get PID of remote: i/o error: pid not found
20251002 10:28:12.450 TZ=+0300 [confighandler:EROR] vpn:158 Failed to communicate with scheduler: ipc error: Timed out
20251002 10:29:02.777 TZ=+0300 [confighandler:EROR] update:27 Failed to communicate with scheduler: ipc error: Timed out
20251002 10:29:29.598 TZ=+0300 [confighandler:EROR] update:27 Failed to communicate with scheduler: ipc error: Timed out
20251002 10:29:33.759 TZ=+0300 [confighandler:EROR] update:27 Failed to communicate with scheduler: ipc error: Timed out
20251002 10:29:35.701 TZ=+0300 [confighandler:EROR] update:27 Failed to communicate with scheduler: ipc error: Timed out
20251002 10:29:35.728 TZ=+0300 [confighandler:EROR] websock:40 Failed to read message: IO error: Broken pipe (os error 32)
20251002 10:29:35.753 TZ=+0300 [confighandler:EROR] update:27 Failed to communicate with scheduler: ipc error: Timed out
20251002 11:02:13.081 TZ=+0300 [confighandler:EROR] update:27 Failed to communicate with scheduler: ipc error: Timed out
20251002 15:40:55.814 TZ=+0300 [confighandler:INFO] main:86 Received signal: SIGTERM
20251002 15:40:55.815 TZ=+0300 [confighandler:INFO] main:68 Webserver shutting down
20251003 08:42:53.158 TZ=+0300 [confighandler:EROR] websock:40 Failed to read message: IO error: Broken pipe (os error 32)
20251003 08:43:03.356 TZ=+0300 [confighandler:EROR] auth:30 Failed to get PID of remote: i/o error: pid not found
20251003 14:02:57.786 TZ=+0300 [confighandler:EROR] decorators:52 Failed to send message to fortitray: runtime directory not found
20251003 14:03:00.801 TZ=+0300 [confighandler:INFO] main:86 Received signal: SIGTERM
20251003 14:03:00.801 TZ=+0300 [confighandler:INFO] main:68 Webserver shutting down
20251003 15:11:49.734 TZ=+0300 [confighandler:EROR] update:27 Failed to communicate with scheduler: ipc error: Connection refused


==> ./fazlogupload.log <==
20251003 15:31:15.416 TZ=+0300 [fazlogupload:EROR] avatar_upload:225 Failed to open cache file: No such file or directory (os error 2)
20251003 15:31:15.416 TZ=+0300 [fazlogupload:INFO] avatar_upload:126 Found new avatar to upload
20251003 15:31:15.416 TZ=+0300 [fazlogupload:INFO] avatar_upload:134 Uploading avatar (size: 10362)
20251003 15:31:15.416 TZ=+0300 [fazlogupload:INFO] faz_comm:36 Connecting to MYVPNENDPOINT (TLS: true)
20251003 15:31:15.422 TZ=+0300 [fazlogupload:EROR] avatar_upload:139 Failed to connect: i/o error: failed to lookup address information: Name or service not known
20251003 15:31:15.422 TZ=+0300 [fazlogupload:EROR] avatar_upload:129 Failed to process avatar: connect failed
20251003 15:32:15.504 TZ=+0300 [fazlogupload:INFO] avatar_upload:181 Found user avatar file at FILE.png
20251003 15:32:15.504 TZ=+0300 [fazlogupload:EROR] avatar_upload:225 Failed to open cache file: No such file or directory (os error 2)
20251003 15:32:15.504 TZ=+0300 [fazlogupload:INFO] avatar_upload:126 Found new avatar to upload
20251003 15:32:15.504 TZ=+0300 [fazlogupload:INFO] avatar_upload:134 Uploading avatar (size: 10362)
20251003 15:32:15.504 TZ=+0300 [fazlogupload:INFO] faz_comm:36 Connecting to MYVPN ENDPOINT (TLS: true)
20251003 15:32:15.509 TZ=+0300 [fazlogupload:EROR] avatar_upload:139 Failed to connect: i/o error: failed to lookup address information: Name or service not known
20251003 15:32:15.510 TZ=+0300 [fazlogupload:EROR] avatar_upload:129 Failed to process avatar: connect failed
20251003 15:33:15.616 TZ=+0300 [fazlogupload:INFO] avatar_upload:181 Found user avatar file at AVATAR.png
20251003 15:33:15.617 TZ=+0300 [fazlogupload:EROR] avatar_upload:225 Failed to open cache file: No such file or directory (os error 2)
20251003 15:33:15.617 TZ=+0300 [fazlogupload:INFO] avatar_upload:126 Found new avatar to upload
20251003 15:33:15.617 TZ=+0300 [fazlogupload:INFO] avatar_upload:134 Uploading avatar (size: 10362)
20251003 15:33:15.617 TZ=+0300 [fazlogupload:INFO] faz_comm:36 Connecting to MYVPNENDPOINT (TLS: true)
20251003 15:33:15.622 TZ=+0300 [fazlogupload:EROR] avatar_upload:139 Failed to connect: i/o error: failed to lookup address information: Name or service not known
20251003 15:33:15.623 TZ=+0300 [fazlogupload:EROR] avatar_upload:129 Failed to process avatar: connect failed

==> ./sslvpn.log <==
20251003 15:33:57.989 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv6.ignore-auto-dns: no
20251003 15:33:58.185 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv4.addresses: MYIP
20251003 15:33:58.382 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv6.addresses:
20251003 15:33:58.591 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv4.routes:
20251003 15:33:58.783 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv6.routes:
20251003 15:33:58.982 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv4.ignore-auto-routes: no
20251003 15:33:59.177 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv6.ignore-auto-routes: no
20251003 15:33:59.373 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv4.dns:
20251003 15:33:59.604 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv6.dns:
20251003 15:33:59.797 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv4.dns-search:
20251003 15:33:59.995 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv6.dns-search:
20251003 15:34:00.220 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv4.ignore-auto-dns: no
20251003 15:34:00.424 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv6.ignore-auto-dns: no
20251003 15:34:00.624 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv4.addresses: MYIP
20251003 15:34:00.834 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv6.addresses:
20251003 15:34:01.050 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv4.routes:
20251003 15:34:01.256 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv6.routes:
20251003 15:34:01.467 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv4.ignore-auto-routes: no
20251003 15:34:01.681 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv6.ignore-auto-routes: no
20251003 15:34:01.882 TZ=+0300 [sslvpn:DEBG] vpn_util:299 Get ipv4.dns:

Announcements
Check out our Community Chatter Blog! Click here to get involved
Labels
Top Kudoed Authors