Hi,
you may have noticed that http://sfepy.org, that should point to [1], either does not work, or points to the main google site. That's because something changed, and my old DNS settings (ip 69.56.173.218) do not work anymore.
I have tried changing the ip to 209.85.227.100 which is what I found to be the new ip of code.google.com (one of many), but that just redirects to google.com.
Is there anyone experienced more with those issues around?
r.
On Tue, Nov 16, 2010 at 1:22 AM, Robert Cimrman <cimr...@ntc.zcu.cz> wrote:
Hi,
you may have noticed that http://sfepy.org, that should point to [1], either does not work, or points to the main google site. That's because something changed, and my old DNS settings (ip 69.56.173.218) do not work anymore.
I have tried changing the ip to 209.85.227.100 which is what I found to be the new ip of code.google.com (one of many), but that just redirects to google.com.
Is there anyone experienced more with those issues around?
r.
That's my fault, as I have removed that linode server (ip 69.56.173.218). You need to create an apache rule to redirect the domain.
Ondrej
On 12/14/10 03:10, Ondrej Certik wrote:
On Tue, Nov 16, 2010 at 1:22 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
Hi,
you may have noticed that http://sfepy.org, that should point to [1], either does not work, or points to the main google site. That's because something changed, and my old DNS settings (ip 69.56.173.218) do not work anymore.
I have tried changing the ip to 209.85.227.100 which is what I found to be the new ip of code.google.com (one of many), but that just redirects to google.com.
Is there anyone experienced more with those issues around?
r.
That's my fault, as I have removed that linode server (ip 69.56.173.218). You need to create an apache rule to redirect the domain.
ok, puzzle solved :). I have completely forgotten that there was an intermediate server.
We moved sfepy.org to our server, and I like the way it is now.
Thanks for clarification.
r.
On Tue, Dec 14, 2010 at 2:04 AM, Robert Cimrman <cimr...@ntc.zcu.cz> wrote:
On 12/14/10 03:10, Ondrej Certik wrote:
On Tue, Nov 16, 2010 at 1:22 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
Hi,
you may have noticed that http://sfepy.org, that should point to [1], either does not work, or points to the main google site. That's because something changed, and my old DNS settings (ip 69.56.173.218) do not work anymore.
I have tried changing the ip to 209.85.227.100 which is what I found to be the new ip of code.google.com (one of many), but that just redirects to google.com.
Is there anyone experienced more with those issues around?
r.
That's my fault, as I have removed that linode server (ip 69.56.173.218). You need to create an apache rule to redirect the domain.
ok, puzzle solved :). I have completely forgotten that there was an intermediate server.
We moved sfepy.org to our server, and I like the way it is now.
Thanks for clarification.
Cool! I use github these days, e.g. sympy.org is *fully* hosted by github.
Ondrej
On 12/14/10 21:39, Ondrej Certik wrote:
On Tue, Dec 14, 2010 at 2:04 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
On 12/14/10 03:10, Ondrej Certik wrote:
On Tue, Nov 16, 2010 at 1:22 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
Hi,
you may have noticed that http://sfepy.org, that should point to [1], either does not work, or points to the main google site. That's because something changed, and my old DNS settings (ip 69.56.173.218) do not work anymore.
I have tried changing the ip to 209.85.227.100 which is what I found to be the new ip of code.google.com (one of many), but that just redirects to google.com.
Is there anyone experienced more with those issues around?
r.
That's my fault, as I have removed that linode server (ip 69.56.173.218). You need to create an apache rule to redirect the domain.
ok, puzzle solved :). I have completely forgotten that there was an intermediate server.
We moved sfepy.org to our server, and I like the way it is now.
Thanks for clarification.
Cool! I use github these days, e.g. sympy.org is *fully* hosted by github.
We are also drifting towards github. By *fully* you mean also mailing lists and issue tracking?
r.
On Wed, Dec 15, 2010 at 1:58 AM, Robert Cimrman <cimr...@ntc.zcu.cz> wrote:
On 12/14/10 21:39, Ondrej Certik wrote:
On Tue, Dec 14, 2010 at 2:04 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
On 12/14/10 03:10, Ondrej Certik wrote:
On Tue, Nov 16, 2010 at 1:22 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
Hi,
you may have noticed that http://sfepy.org, that should point to [1], either does not work, or points to the main google site. That's because something changed, and my old DNS settings (ip 69.56.173.218) do not work anymore.
I have tried changing the ip to 209.85.227.100 which is what I found to be the new ip of code.google.com (one of many), but that just redirects to google.com.
Is there anyone experienced more with those issues around?
r.
That's my fault, as I have removed that linode server (ip 69.56.173.218). You need to create an apache rule to redirect the domain.
ok, puzzle solved :). I have completely forgotten that there was an intermediate server.
We moved sfepy.org to our server, and I like the way it is now.
Thanks for clarification.
Cool! I use github these days, e.g. sympy.org is *fully* hosted by github.
We are also drifting towards github. By *fully* you mean also mailing lists and issue tracking?
By "fully" I meant that github hosts the web pages behind sympy.org, so I don't need my own server to redirect anything.
Ondrej
On 12/15/10 22:34, Ondrej Certik wrote:
On Wed, Dec 15, 2010 at 1:58 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
On 12/14/10 21:39, Ondrej Certik wrote:
On Tue, Dec 14, 2010 at 2:04 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
On 12/14/10 03:10, Ondrej Certik wrote:
On Tue, Nov 16, 2010 at 1:22 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
Hi,
you may have noticed that http://sfepy.org, that should point to [1], either does not work, or points to the main google site. That's because something changed, and my old DNS settings (ip 69.56.173.218) do not work anymore.
I have tried changing the ip to 209.85.227.100 which is what I found to be the new ip of code.google.com (one of many), but that just redirects to google.com.
Is there anyone experienced more with those issues around?
r.
That's my fault, as I have removed that linode server (ip 69.56.173.218). You need to create an apache rule to redirect the domain.
ok, puzzle solved :). I have completely forgotten that there was an intermediate server.
We moved sfepy.org to our server, and I like the way it is now.
Thanks for clarification.
Cool! I use github these days, e.g. sympy.org is *fully* hosted by github.
We are also drifting towards github. By *fully* you mean also mailing lists and issue tracking?
By "fully" I meant that github hosts the web pages behind sympy.org, so I don't need my own server to redirect anything.
I see, thanks.
r.
participants (2)
-
Ondrej Certik -
Robert Cimrman