topic Re: Issues accessing *.graphisoft.com? in Installation & update

Issues accessing *.graphisoft.com?

Ebatte — Fri, 19 Apr 2024 02:28:24 GMT

Anyone else having issues over the past few days accessing anything on Graphisoft's web site including www.graphisoft.com , BIMx.graphisoft.com , etc?

Operating system used: Mac Apple Silicon

Re: Issues accessing *.graphisoft.com?

Karl Ottenstein — Thu, 18 Apr 2024 15:03:46 GMT

Could you describe the issues, Eric? I’ve had issues with being redirected to the US site when trying to view other localized sites… and with the button on the US home page for the upcoming Building Together webinar doing nothing…

Re: Issues accessing *.graphisoft.com?

Barry Kelly — Fri, 19 Apr 2024 01:23:08 GMT

I just tried you link and got server not found.

But this link worked fine ... https://graphisoft.com/

Is 'www.' not a thing any more?

Barry.

Re: Issues accessing *.graphisoft.com?

Ebatte — Fri, 19 Apr 2024 02:16:40 GMT

If you click on the link in my message the url is malformed because the comma gets included. Anyway, as I described the site sometimes loads and sometimes doesn’t.

Re: Issues accessing *.graphisoft.com?

Barry Kelly — Fri, 19 Apr 2024 02:29:29 GMT

I have edited the comma out in your link, and now it does work for me.

Barry.

Re: Issues accessing *.graphisoft.com?

Lingwisyer — Fri, 19 Apr 2024 06:29:22 GMT

Maybe a bad database at one of your routes? Tried a different computer? See if it works for you over a hotspot / tether? If so, maybe try changing your DNS or cycling your router to get a new external IP.

Re: Issues accessing *.graphisoft.com?

Noemi Balogh — Fri, 19 Apr 2024 07:31:38 GMT

We're not familiar with any on-going access issues at the moment (the two things we knew about are Karl's report and the - both are under investigation at the moment). Could you please share a screenshot about what you see?

Also Lingwisyer had some good tips, please check those too.

Re: Issues accessing *.graphisoft.com?

Ebatte — Tue, 23 Apr 2024 14:38:23 GMT

Disregard. It appears that whitelisting certain regions/countries on our network cleared the issue.