<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>weather.com portal fails when connecting to Horde via HTTPS</title> 
  <pubDate>Fri, 10 Apr 2026 13:16:43 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/7028</link> 
  <atom:link rel="self" type="application/rss+xml" title="weather.com portal fails when connecting to Horde via HTTPS" href="https://bugs.horde.org/ticket/7028/rss" /> 
  <description>weather.com portal fails when connecting to Horde via HTTPS</description> 
 
   
   
  <item> 
   <title>It appears that the plugin for weather.com is perhaps genera</title> 
   <description>It appears that the plugin for weather.com is perhaps generating its URLs based partially on how the user connects to Horde itself. When I connect to my Horde website via HTTPS, I get a -12263 error. I was getting this ONLY with Horde and ONLY when using HTTPS. In addition to the fact that I did not get it on the login page, and I ONLY received it when my portal contained the weather.com plugin. Once I removed it, the error went away.</description> 
   <pubDate>Sun, 06 Jul 2008 03:37:36 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7028#t47246</link> 
  </item> 
   
  <item> 
   <title>It works fine here over HTTPS. Beside that, the data retriev</title> 
   <description>It works fine here over HTTPS. Beside that, the data retrieval is completely encapsulated in the Service_Weather package from PEAR.</description> 
   <pubDate>Sun, 06 Jul 2008 08:40:04 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7028#t47247</link> 
  </item> 
   
  <item> 
   <title>&gt; It works fine here over HTTPS. Beside that, the data retri</title> 
   <description>&gt; It works fine here over HTTPS. Beside that, the data retrieval is 

&gt; completely encapsulated in the Service_Weather package from PEAR.



Hmm, yes you&#039;re right it&#039;s not the weather.com stuff right now. It was coincidental that it stopped then. It just started giving me this error again.



Apparently it was, oddly enough, an outdated config causing this error. Maybe something was making apache or php whine too much because something was or wasn&#039;t set properly? I believe it was either turba or trean that started giving me this. I regenerated the config from the setup admin menu and got that error. But I have not got it since. So far.</description> 
   <pubDate>Sun, 06 Jul 2008 16:12:45 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7028#t47252</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
