Jsezze

You’ll have to further expand on what you mean by “But new host is not working.” as that could mean anything. Do you see any errors when accessing the site or in your PHP/Apache error logs?

The only way it’d force you through HTTPS is if your site config is configured to do so or you enabled the Force HTTPS setting in the system before dumping the database originally.

I think we really need to drill down on what exactly “isn’t working” first.

Cheers.

      KevinTheJedi Thanks for your response so quickly, Kevin.

      Is not working = can not open the URL

      It looks like newdomain.example.com closed the connection
Try:

Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics
ERR_CONNECTION_CLOSED

      It seems like an issue of SSL, I will double-check again.

      Thank you.

          Jsezze

          You should first try to ping the domain from your local PC. If that doesn’t connect then you can flush your local DNS, go to your local DNS and add a record pointing the domain to the public IP, and try the ping again. If it still doesn’t work either contact your hosting provider and/or ISP for further assistance.

          If the ping does work then you can flush your cache/cookies/etc. in the browser and try accessing the site once more. It may also be worth trying to connect to the site using an entirely different network as your ISP may be blocking it, etc.

          Cheers.

              KevinTheJedi I also use CloudFlare with DNS Only, the ping is fine. I will try to make a full new backup without forcing the HTTPS setting, even rebuild a whole new osTicket 1.18.1, and recover the old database to see what is the next situation.

              Thank you

                  Jsezze

                  If you do a new install and then go to restore the database make sure you copy over the old include/ost-config.php file to the same folder in new install and update it with the new info (if anything changed). It contains the secret salt, etc.

                  Cheers.

                      KevinTheJedi Resolve the issue already, it's about the feature of Force all requests through HTTPS,
                      before moving out it needs to be disabled if the new host with a new domain and no SSL certificate.

                      Step:

                      1. Disable the feature Force HTTPS before making a full folder backup of osticket
                      2. mysqldump backup database on the server directly without downloading and uploading

                      thanks for your time, Kevin.

                      Cheers

                        KevinTheJedi

                        Hello Kevin,

                        May I ask you for one more extra experience about the CloudFlare Proxied + osTicket Force all requests through HTTPS? What if I don't want to install an SSL certificate on my server and hide the real server IP address?

                        • CloudFlare proxied - enable
                        • osTicket system Force all requests through HTTPS

                        I've tried this way but got an error of 521 web server is down.

                        Thank you.

                            Jsezze

                            I personally know nothing about Cloudflare so I wouldn’t be able to assist with anything related to that. However as a general standard, you shouldn’t be forcing HTTPS without a valid SSL certificate. If you don’t have one, these days it’s super simple to get one. You can generate a legitimate and free SSL certificate using something like Let'sEncrypt.

                            Cheers.

                                Jsezze

                                It’s not required but it’s good to fill that out to ensure best functionality.

                                Cheers.

                                  11 days later

                                  I am trying to configure a new osTicket 1.18.1 on a separate server on ubuntu 22.04 and i also have old osticket version
                                  v1.15.4 and i tried to take the mysql dump of old version to a newer osTicket 1.18.1 because i require the old data to be reflected in a newer osticket version during osticket installation it showed that MYSQL table prefix ost_ is already presented so i change to osnew_ now i have old db mysql table prefix and new table prefix also everything went fine but when i tried to open the new osticket portal it doesn't work at all just give errors like

                                  Parse error: syntax error, unexpected single-quoted string ");", expecting ")" in /var/www/prod-ticket.example.com/upload/include/ost-config.php on line 51

                                  When i check the ost-config.php the line 51 is already commented out

                                  Is that because of old osticket version v1.15.4 mysql table prefix already presented or its not supported at all in
                                  newer version of osticket osTicket 1.18.1.

                                  Please help I am stuck and not able to fix the osticket portal.

                                    Write a Reply...