Loading Profile...
My feedly page doesnt display correctly.
When I access feedly, i see the attached screen.This happens when i use the feedly URL, whaen I use the feedly button as well.
I’m readerless
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
-
Inappropriate?Hi Sean. Based on what I am seeing in the screenshot, the stylesheet does not seem to load correctly. Can you please try to SHIFT+reload to clear your cache. If for some reason that does not work can you please do view source and see what the <base> tag looks like.
Thanks and sorry about the inconvenience. -
Inappropriate?The shift+refresh had no effect. The base tag from view source is as follows: <base href="http://s3.feeddo.com/production/1.2.4/" />
-
Inappropriate?Ok. Let's try this then:
1) can you please restart your browser to get upgraded to 1.2.8
2) if that upgrade does not address the issue, can you please try to load http://s3.feeddo.com/production/1.2.8... and see if you are able to get the content of this file? -
Inappropriate?FF upgrade add on doesn't detect an 1.2.8 update. the link you provided gives me a "page load error"
-
Inappropriate?Sean: 1.2.4 -> 1.2.8 is a patch and will happen automatically when you restart the browser. The firefox update is only used for major upgrade (1.2.x to 1.3.y).
I do not understand why you are not able to load:
http://s3.feeddo.com/production/1.2.8...
or http://s3.feeddo.com/production/1.2.4...
These are just static files and I just tried from 7 different places and had no problem accessing them. Can you please confirm that get satisfaction did not change somehow the url and that you are trying to load:
s3.feeddo.com/production/1.2.8/styles/feedly.css
or s3.feeddo.com/production/1.2.4/styles/feedly.css
Do you use a proxy or something to access the internet? -
Inappropriate?Edwin, no proxy.
I tried to uninstall and reinstall the plugin. No change. I am not able to access the two above links.
-
Inappropriate?Hmm...Ok. We are reaching the limits of my competence. Our ops person will be in this afternoon and I will ask him what could be causing this.
One last test. The DNS server should translate the above address to:
http://feeddo.fileburst.com/productio...
Can you please let me know if you are able to access this address? This would help me know if it is a DNS problem or something else.
Thanks and again sorry not being able to be more helpful. -
Inappropriate?EK, no dice. Same page load error.
-
Inappropriate?Ok. thank you very much for your time helping troubleshoot this. I will ask our ops person to follow up with fileburst and try to determine why the service is not accessible from special places. Will try to give you an update today or tomorrow.
-
Inappropriate?Hi Sean,
could you give us your public facing IP address ( you can get it here : http://whatismyip.com/ ) and a traceroute ( from the windows terminal : tracert s3.feeddo.com ).
Just to be sure it's a network issue could you also try to load this
http://s3.feeddo.com/production/1.2.8... in IE
Thanks
Olivier -
Inappropriate?sure. My IP addy is 71.231.107.142 .
Tracert:C:\Windows\System32>tracert s3.feeddo.com
Tracing route to feeddo.fileburst.com [69.65.108.119]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 24 ms 10 ms ge-1-4-ur01.seattle.wa.seattle.comcast.net [68.8
6.99.41]
4 10 ms 19 ms 18 ms te-8-4-ar01.burien.wa.seattle.comcast.net [68.86
.96.189]
5 117 ms 17 ms 9 ms 68.86.90.222
6 15 ms 17 ms 14 ms 68.86.90.221
7 28 ms 33 ms 28 ms pos-0-7-0-0-cr01.sacramento.ca.ibone.comcast.net
[68.86.85.201]
8 31 ms 32 ms 46 ms pos-0-6-0-0-cr01.sanjose.ca.ibone.comcast.net [6
8.86.85.78]
9 31 ms 32 ms 33 ms Tenge13-3.br02.sjo01.pccwbtn.net [63.218.179.25]
10 111 ms 110 ms 111 ms dtg.ge10-2.br02.ash01.pccwbtn.net [63.218.94.150
]
11 111 ms 113 ms 112 ms colo4a.iad.keepitsecure.net [69.65.112.14]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
FYI still cant access the s3 feedo link. -
Inappropriate?Thanks Sean for the info.
What I can see so far is that your traceroute doesn't end like it should.
It finds the last router but not the final destination, it should end like that:
"12 apollo.fileburst.net (69.65.108.119)"
We have contacted our hosted file provider to try to address the issue.
I'll update the post as soon as I get some information from them.
1 person says
this solves the problem
-
Inappropriate?Hi Sean,
Our file hosting company just replied telling they fixed the issue.
Could you please try if it is working now ?
Thanks
1 person says
this solves the problem
-
-
Inappropriate?Thanks Oliv. Good to see this issue resolved.
EMPLOYEE
EMPLOYEE
