Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Pfsense Date & Time

    Scheduled Pinned Locked Moved Captive Portal
    55 Posts 9 Posters 42.2k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      muswellhillbilly
      last edited by

      Ok, so it didn't work. What steps did you take to check that it didn't work? Have you checked the date/time in the BIOS at startup? Have you checked that the correct timezone is set as suggested by ishtiaqaj? For that matter, what date/time are you getting? Is it the correct date but out of sync by a few hours? Or is it set to something like 1990? The latter would suggest a CMOS battery issue.

      1 Reply Last reply Reply Quote 0
      • A
        Ashutosh Jain
        last edited by

        @muswellhillbilly:

        Ok, so it didn't work. What steps did you take to check that it didn't work? Have you checked the date/time in the BIOS at startup? Have you checked that the correct timezone is set as suggested by ishtiaqaj? For that matter, what date/time are you getting? Is it the correct date but out of sync by a few hours? Or is it set to something like 1990? The latter would suggest a CMOS battery issue.

        Steps -: General Setup -> Timezone -> Choose timezone then reboot or power off or on the pfsense.
        No i'm not getting correct date it show me old date & time Fri Jan 1 4:10:52 UTC 2010, Their is no CMOS battery issue.

        1 Reply Last reply Reply Quote 0
        • M
          muswellhillbilly
          last edited by

          @ashi_220:

          No i'm not getting correct date it show me old date & time Fri Jan 1 4:10:52 UTC 2010, Their is no CMOS battery issue.

          Your time is over six years out. I repeat, have you checked the date/time in your system BIOS at bootup?

          1 Reply Last reply Reply Quote 0
          • A
            Ashutosh Jain
            last edited by

            @muswellhillbilly:

            @ashi_220:

            No i'm not getting correct date it show me old date & time Fri Jan 1 4:10:52 UTC 2010, Their is no CMOS battery issue.

            Your time is over six years out. I repeat, have you checked the date/time in your system BIOS at bootup?

            Yeah, Now it is changed & show me current date & time. I change Date/time in BIOS settings.
            But one thing that how it is changed & getting six year old date/time when i was not change any date/time settings??

            Thank u very much :)

            1 Reply Last reply Reply Quote 0
            • C
              cmb
              last edited by

              Configure a NTP server under System>General Setup.

              1 Reply Last reply Reply Quote 0
              • M
                muswellhillbilly
                last edited by

                @ashi_220:

                how it is changed & getting six year old date/time when i was not change any date/time settings??

                My guess is that your CMOS battery may be running low generally, though maybe not enough to bomb out completely. Might be worth replacing it in the long run, and also do what cmb suggests and set an NTP server in your settings.

                1 Reply Last reply Reply Quote 0
                • A
                  Ashutosh Jain
                  last edited by

                  @cmb:

                  Configure a NTP server under System>General Setup.

                  Already configure NTP server.

                  1 Reply Last reply Reply Quote 0
                  • A
                    Ashutosh Jain
                    last edited by

                    @muswellhillbilly:

                    @ashi_220:

                    how it is changed & getting six year old date/time when i was not change any date/time settings??

                    My guess is that your CMOS battery may be running low generally, though maybe not enough to bomb out completely. Might be worth replacing it in the long run, and also do what cmb suggests and set an NTP server in your settings.

                    I think their may be issue of CMOS battery. I had already configure NTP server.

                    1 Reply Last reply Reply Quote 0
                    • S Samuel BF referenced this topic on
                    • C
                      Cleetus Antony @Iahmad
                      last edited by

                      @Iahmad
                      I have the same issue. My BIOS time is correct.
                      Is there anyway I can set time by command prompt.

                      E GertjanG 2 Replies Last reply Reply Quote 0
                      • E
                        elvisimprsntr @Cleetus Antony
                        last edited by

                        @Cleetus-Antony said in Pfsense Date & Time:

                        I have the same issue. My BIOS time is correct.

                        Is your BIOS time UTC or local?

                        Linux/FreeBSD requires it to be UTC time

                        Then make sure to configure the correct timezone for your location.

                        C 1 Reply Last reply Reply Quote 0
                        • GertjanG
                          Gertjan @Cleetus Antony
                          last edited by

                          @Cleetus-Antony

                          And why wouldn't the pfSense build in NTP client work for you ?
                          Or isn't your pfSense connected to the Internet ?

                          No "help me" PM's please. Use the forum, the community will thank you.
                          Edit : and where are the logs ??

                          C 1 Reply Last reply Reply Quote 0
                          • C
                            Cleetus Antony @Gertjan
                            last edited by

                            @Gertjan PFSENSE connected to internet and everything is working. Clients r getting internet thru pfsense. When I want to create rules with scheduler, due to time wrong time, the rule doesnt work as indented for clients. Any clue ?

                            1 Reply Last reply Reply Quote 0
                            • C
                              Cleetus Antony @elvisimprsntr
                              last edited by

                              @elvisimprsntr
                              I set the correct time zone in pfsense. Date is correct. but the time is few hours difference. Looks like the time in BIOS is local. there is no option I can see in BIOS to change to UTC. What am I missing ?

                              E 2 Replies Last reply Reply Quote 0
                              • E
                                elvisimprsntr @Cleetus Antony
                                last edited by

                                This post is deleted!
                                1 Reply Last reply Reply Quote 0
                                • E
                                  elvisimprsntr @Cleetus Antony
                                  last edited by

                                  @Cleetus-Antony

                                  simply set the BIOS time to UTC HH:MM:SS

                                  https://www.timeanddate.com/worldclock/timezone/utc

                                  C 2 Replies Last reply Reply Quote 1
                                  • C
                                    Cleetus Antony @elvisimprsntr
                                    last edited by

                                    @elvisimprsntr
                                    Time in BIOS is correct and its in UTC format. Still I installed new battery in motherboard.
                                    But even after setting correct time zone in pfsense, time is 7 Hours ahead.

                                    E 1 Reply Last reply Reply Quote 0
                                    • E
                                      elvisimprsntr @Cleetus Antony
                                      last edited by

                                      @Cleetus-Antony

                                      1. GUI: stop NTP service
                                      2. CLI: ntpdate time.nist.gov
                                      3. GUI: restart NTP service
                                      C 3 Replies Last reply Reply Quote 0
                                      • C
                                        Cleetus Antony @elvisimprsntr
                                        last edited by

                                        This post is deleted!
                                        1 Reply Last reply Reply Quote 0
                                        • C
                                          Cleetus Antony @elvisimprsntr
                                          last edited by

                                          @elvisimprsntr

                                          Did the same. I got below msg on output.
                                          Still the time is wrong.. Now 4 Hours 30 min difference.

                                          14 Jun 19:03:04 ntpdate[63408]: the NTP socket is in use, exiting

                                          1 Reply Last reply Reply Quote 0
                                          • C
                                            Cleetus Antony @elvisimprsntr
                                            last edited by

                                            @elvisimprsntr
                                            14 Jun 19:14:57 ntpdate[69805]: no server suitable for synchronization found

                                            this is the result of second try

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.