Well, the original question was, how to see weewx from a public ip. I must 
confess, that I did not think about security issues and just did it this 
way:
I used a IPv6 only DNS from dynv6.com. So I could readily access 
http://raspbee.example.dynv6.net:8000/weewx/index.html from outside. So 
far, I have never observed any intrusion or hack or what ever since more 
than a year running. 

But currently I doubt, that this is a trustful solution. In order to 
replace http by https, I have installed a letsencrypt solution using 
dehydrated plus a dynv6 specific hook, which updates the pem files. I have 
tested it with my home-assistant setup, which works pretty fine.
So, I thought,  when https://raspbee.example.dynv6.net:8123 works,  
https://raspbee.example.dynv6.net:8000/weewx/index.html should work also.
I tried to edit /etc/lighttpd.conf according to some prescription, I found 
in the net. But, it failed because port 443 is already in use. I thought, 
this would be an IPv4 related problem and looked for another conf file with 
repsect to IPv6 at https://blog.mro.name/2022/04/lighttpd-ipv6/. Of Course, 
I adopted the paths to my conditions. But, unfortunately I still get the 
error message

source: /etc/lighttpd/conf-available/12-tls-dehydrated.sh line: 1 pos: 9 
parser failed somehow near here: [

which has no meaning for me. Yes, I am dumb concerning https.
I am afraid, that I will have to go manually through all the ssl specific 
entries in lighttpd configuration to let it work. May be, there is someone, 
that could guide me.

Thanks
Peter

kb3...@gmail.com schrieb am Samstag, 7. Januar 2023 um 10:45:45 UTC+1:

> I have a couple domain names from google domains for the couple websites I 
> have.  The raspberry pi just runs weewx to upload my weather station to 
> some of the options on there and the pi also has a broadcastify scanner 
> feed that I have on there.   
>
> On Friday, January 6, 2023 at 8:25:18 AM UTC-5 Cameron D wrote:
>
>> Are you saying that you have a registered domain name (and that is as far 
>> as you have gone), or that you have a web server that is already 
>> successfully serving other pages to the public internet? 
>>  What exactly is that raspberry pi doing?  If it is serving web pages, is 
>> it the same machine that is running weewx?
>>
>> On Friday, 6 January 2023 at 6:35:21 pm UTC+10 kb3...@gmail.com wrote:
>>
>>> Lots of info.  Thanks.  I  have a website domain already and use a 
>>> raspberry pi for this.  I apparently just can't seem to get it to show 
>>> other than on the local network.  
>>>
>>> On Thursday, January 5, 2023 at 12:13:20 PM UTC-5 pannetron wrote:
>>>
>>>> If you host a public website from a personal Linux server, as I do, 
>>>> look into using fail2ban as a way to detect and block some bad actor bots. 
>>>>  
>>>> My implementation currently has about 2500 IPs blocked because they were 
>>>> looking for typical webserver security flaws.
>>>>
>>>> On Wednesday, January 4, 2023 at 11:11:49 AM UTC-7 
>>>> do...@dougjenkins.com wrote:
>>>>
>>>>> Glad some of you find this useful.
>>>>>
>>>>> I have been using this method since it came out this summer (July 
>>>>> 2022). I run my infrastructure (Web Server, WeeWX, MQTT, MariaDB) as 
>>>>> containers in one stack in its own network all in Docker. I do this to 
>>>>> limit what the cloudflare tunnel can access on my network (just WeeWx 
>>>>> stuff). All of this works in docker in one stack and one YAML file!
>>>>>
>>>>> Like Tom Lawerence mentioned in the video I attached, you have to put 
>>>>> Cloudflare in your "circle of trust" as you are depending on them for 
>>>>> both 
>>>>> the client and server/edge side of the tunnel. You have to make that 
>>>>> determination on your own if you are comfortable with that.
>>>>>
>>>>> As other methods mentioned here, they are all great alternatives. I 
>>>>> was not aware adafriut offered a dashboard to present your data. That can 
>>>>> be a good alternative than going through the hassle of hosting a full 
>>>>> website for your station.
>>>>>
>>>>> If I get a free moment in a few weeks, I can post a step-by-step 
>>>>> article on onboarding your WeeWX weather station as a public website 
>>>>> using 
>>>>> Cloudflare. I think it can help a lot of users who struggle with the 
>>>>> network & security setup.
>>>>>
>>>>> DDJ
>>>>>
>>>>> On Wed, Jan 4, 2023 at 12:49 PM vince <vince...@gmail.com> wrote:
>>>>>
>>>>>> On Tuesday, January 3, 2023 at 6:41:01 PM UTC-8 do...@dougjenkins.com 
>>>>>> wrote:
>>>>>>
>>>>>>> If you are willing to roll up your sleeves and get technical, 
>>>>>>> serving your website at home can be done safely and securely without 
>>>>>>> changing your firewall. There are some steps to do, but at the end it 
>>>>>>> will 
>>>>>>> save you money and it will give you some real-world IT experience.
>>>>>>>
>>>>>>>
>>>>>> Very cool - thanks for the pointer to the video.  I hadn't previously 
>>>>>> figured out the Zero Trust terminology enough to try the tunnel stuff. 
>>>>>> I'll 
>>>>>> have to try the tunnel thing too !!!!
>>>>>>
>>>>>> For the original poster, Doug's steps 1-3 are very easy.  I'd 
>>>>>> previously done that using Google Domains ($12/year).
>>>>>>
>>>>>> Note - you probably still want to possibly harden your weewx 
>>>>>> webserver a bit.  There are zillions of bots trying to attack web 
>>>>>> servers 
>>>>>> 'especially' all things WordPress.  If you go just with a vanilla weewx 
>>>>>> setup you're likely in very good shape straight out of the box.  Cool 
>>>>>> cheap 
>>>>>> option for sure.
>>>>>>
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "weewx-user" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to weewx-user+...@googlegroups.com.
>>>>>>
>>>>> To view this discussion on the web visit 
>>>>>> https://groups.google.com/d/msgid/weewx-user/56afd382-a9ba-49e7-831f-2813872d6db0n%40googlegroups.com
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/weewx-user/56afd382-a9ba-49e7-831f-2813872d6db0n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>>
>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b447988c-0527-40ba-b516-5139cfb733b1n%40googlegroups.com.

Reply via email to