Menu
▾
▴
astlinux-users
|
From: Steve B. <ste...@gm...> - 2022-04-16 22:25:16
|
Hello there everyone, I am a ‘very basic level user’ who has been successfully using Astlinux for approx. the last 5 years, for the interconnection of my heritage telephones and communication with other enthusiasts. I recently updated the firmware on my HP T5720 Thin Client PC to Astlinux 1.3.8 along with Asterisk 13.31.0 However, now after rebooting/restarting I have ‘lost’ my Web Interface to the ‘Astlinux Management’ page. I used to access this by entering in my Google Chrome Browser: https://192.168.1.141/status.php But I now get the message returned: /This site can’t be reached// //192.168.1.141 took too long to respond.// /// However, the good news is that I can still make and receive calls etc. etc. and can SSH access to all my folders/files via Putty or access them via WinSCP using SFTP Any ideas anyone on how I can access the ‘Astlinux Management’ GUI again without doing total reinstall? Best wishes Steve - UK |
|
From: Michael K. <li...@mk...> - 2022-04-17 09:13:41
|
> Am 17.04.2022 um 00:25 schrieb Steve Barlow <ste...@gm...>: > > Hello there everyone, I am a ‘very basic level user’ who has been successfully using Astlinux for approx. the last 5 years, for the interconnection of my heritage telephones and communication with other enthusiasts. > > I recently updated the firmware on my HP T5720 Thin Client PC to Astlinux 1.3.8 along with Asterisk 13.31.0 > > However, now after rebooting/restarting I have ‘lost’ my Web Interface to the ‘Astlinux Management’ page. > > I used to access this by entering in my Google Chrome Browser: > > https://192.168.1.141/status.php Hi Steve, do you have tried: https://192.168.1.141/admin/status.php If it fails, maybe lighttpd (the webserver) is not running. You can try via ssh: ps | grep lighttpd 1442 root lighttpd -f /etc/lighttpd.conf 5144 root grep lighttpd The first line shows here that lighttpd is running (1442), if not try this to start lighttpd: service lighttpd stop service lighttpd init > But I now get the message returned: > > This site can’t be reached > 192.168.1.141 took too long to respond. > > However, the good news is that I can still make and receive calls etc. etc. and can SSH access to all my folders/files via Putty or access them via WinSCP using SFTP > > Any ideas anyone on how I can access the ‘Astlinux Management’ GUI again without doing total reinstall? > > Best wishes > Steve - UK Michael http://www.mksolutions.info |
|
From: Steve B. <ste...@gm...> - 2022-04-17 09:48:53
|
Thanks for your reply Michael
I tried
*/https://192.168.1.141/admin/status.php /*
But still no joy....
Please see below the response I got when I input your suggestions via putty
*/pbx ~ #/*
*//*
*/pbx ~ # ps | grep lighttpd/*
*//*
*//**/1848 root/**//**/grep lighttpd/*
*//**/
/**//*
*/pbx ~ #/*
*//*
*/pbx ~ # service lighttpd stop/*
*//*
*/pbx ~ # service lighttpd init/*
*//*
*/Starting lighttpd.../*
*//*
*//*
*//*
*/WARNING WARNING WARNING/*
*//*
*/ YOU STILL HAVE NOT CHANGED YOUR HTTPS ADMIN PASSWORD/*
*//*
*/ANYONE THAT KNOWS YOU ARE USING ASTLINUX CAN DESTROY YOUR/*
*//*
*/SYSTEM. PLEASE CHANGE THIS OR DISABLE THE HTTPS ADMIN/*
*//*
*/INTERFACE IMMEDIATELY!/*
*//*
*/ Example:/*
*//*
*/ htpasswd /var/www/admin/.htpasswd admin/*
*//*
*/ WARNING WARNING WARNING/*
*//*
*//*
*//*
*/2022-04-17 10:37:01: (mod_openssl.c.427) SSL:
BIO_read_filename('/etc/ssl/AstLinux.pem') failed/*
*//*
*/2022-04-17 10:37:01: (server.c.1161) Initialization of plugins failed.
Going down./*
*//*
*/pbx ~ #/*
*//*
Best wishes
Steve.
On 17/04/2022 10:13, Michael Keuter wrote:
>> Am 17.04.2022 um 00:25 schrieb Steve Barlow<ste...@gm...>:
>>
>> Hello there everyone, I am a ‘very basic level user’ who has been successfully using Astlinux for approx. the last 5 years, for the interconnection of my heritage telephones and communication with other enthusiasts.
>>
>> I recently updated the firmware on my HP T5720 Thin Client PC to Astlinux 1.3.8 along with Asterisk 13.31.0
>>
>> However, now after rebooting/restarting I have ‘lost’ my Web Interface to the ‘Astlinux Management’ page.
>>
>> I used to access this by entering in my Google Chrome Browser:
>>
>> https://192.168.1.141/status.php
> Hi Steve,
> do you have tried:
>
> https://192.168.1.141/admin/status.php
>
> If it fails, maybe lighttpd (the webserver) is not running. You can try via ssh:
>
> ps | grep lighttpd
> 1442 root lighttpd -f /etc/lighttpd.conf
> 5144 root grep lighttpd
>
> The first line shows here that lighttpd is running (1442), if not try this to start lighttpd:
>
> service lighttpd stop
> service lighttpd init
>
>> But I now get the message returned:
>>
>> This site can’t be reached
>> 192.168.1.141 took too long to respond.
>>
>> However, the good news is that I can still make and receive calls etc. etc. and can SSH access to all my folders/files via Putty or access them via WinSCP using SFTP
>>
>> Any ideas anyone on how I can access the ‘Astlinux Management’ GUI again without doing total reinstall?
>>
>> Best wishes
>> Steve - UK
> Michael
>
> http://www.mksolutions.info
>
>
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal top...@kr.... |
|
From: Steve B. <ste...@gm...> - 2022-04-17 20:42:21
|
Problem solved – thanks Michael 👍
Your suggestion that by using SSH via WinSCP to re-start lighttpd by inputting
*/service lighttpd stop service lighttpd init/*
resulted in the following message:
*/2022-04-17 10:37:01: (mod_openssl.c.427) SSL:
BIO_read_filename('/etc/ssl/AstLinux.pem') failed
/*On investigation the file /etc/ssl/AstLinux.pem was not there on the
my file system
Then by using the /etc/ssl/default_https.pem file that was there, I
copied the “default_https.pem” file and renamed it to "AstLinux.pem" and
so it was there now.
Rebooted and this solved the problem - https://192.168.1.141/status.php
now works fine
I’m not sure if any of that makes sense but this may help:
Before – when I couldn’t access the Web Interface GUI Management Page
After – problem solved
So – thanks once again
Best wishes
Steve
On 17/04/2022 11:10, Michael Keuter wrote:
> Let's wait for Lonnie to chime in - in a few hours.
>
>> Am 17.04.2022 um 11:48 schrieb Steve Barlow<ste...@gm...>:
>>
>> Thanks for your reply Michael
>>
>> I tried
>>
>> https://192.168.1.141/admin/status.php
>> But still no joy....
>>
>>
>> Please see below the response I got when I input your suggestions via putty
>>
>> pbx ~ #
>>
>> pbx ~ # ps | grep lighttpd
>>
>> 1848 root grep lighttpd
>>
>>
>> pbx ~ #
>>
>> pbx ~ # service lighttpd stop
>>
>> pbx ~ # service lighttpd init
>>
>> Starting lighttpd...
>>
>>
>>
>> WARNING WARNING WARNING
>>
>> YOU STILL HAVE NOT CHANGED YOUR HTTPS ADMIN PASSWORD
>>
>> ANYONE THAT KNOWS YOU ARE USING ASTLINUX CAN DESTROY YOUR
>>
>> SYSTEM. PLEASE CHANGE THIS OR DISABLE THE HTTPS ADMIN
>>
>> INTERFACE IMMEDIATELY!
>>
>> Example:
>>
>> htpasswd /var/www/admin/.htpasswd admin
>>
>> WARNING WARNING WARNING
>>
>>
>>
>> 2022-04-17 10:37:01: (mod_openssl.c.427) SSL: BIO_read_filename('/etc/ssl/AstLinux.pem') failed
>>
>> 2022-04-17 10:37:01: (server.c.1161) Initialization of plugins failed. Going down.
>>
>> pbx ~ #
>>
>>
>> Best wishes
>> Steve.
>>
>>
>>
>>
>>
>>
>> On 17/04/2022 10:13, Michael Keuter wrote:
>>>> Am 17.04.2022 um 00:25 schrieb Steve Barlow<ste...@gm...>
>>>> :
>>>>
>>>> Hello there everyone, I am a ‘very basic level user’ who has been successfully using Astlinux for approx. the last 5 years, for the interconnection of my heritage telephones and communication with other enthusiasts.
>>>>
>>>> I recently updated the firmware on my HP T5720 Thin Client PC to Astlinux 1.3.8 along with Asterisk 13.31.0
>>>>
>>>> However, now after rebooting/restarting I have ‘lost’ my Web Interface to the ‘Astlinux Management’ page.
>>>>
>>>> I used to access this by entering in my Google Chrome Browser:
>>>>
>>>>
>>>> https://192.168.1.141/status.php
>>> Hi Steve,
>>> do you have tried:
>>>
>>>
>>> https://192.168.1.141/admin/status.php
>>>
>>>
>>> If it fails, maybe lighttpd (the webserver) is not running. You can try via ssh:
>>>
>>> ps | grep lighttpd
>>> 1442 root lighttpd -f /etc/lighttpd.conf
>>> 5144 root grep lighttpd
>>>
>>> The first line shows here that lighttpd is running (1442), if not try this to start lighttpd:
>>>
>>> service lighttpd stop
>>> service lighttpd init
>>>
>>>
>>>> But I now get the message returned:
>>>>
>>>> This site can’t be reached
>>>> 192.168.1.141 took too long to respond.
>>>>
>>>> However, the good news is that I can still make and receive calls etc. etc. and can SSH access to all my folders/files via Putty or access them via WinSCP using SFTP
>>>>
>>>> Any ideas anyone on how I can access the ‘Astlinux Management’ GUI again without doing total reinstall?
>>>>
>>>> Best wishes
>>>> Steve - UK
>>>>
>>> Michael
>>>
>>>
>>> http://www.mksolutions.info
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Astlinux-users mailing list
>>>
>>> Ast...@li...
>>> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>>>
>>>
>>> Donations to support AstLinux are graciously accepted via PayPal to
>>> pa...@kr....
>
> Michael
>
> http://www.mksolutions.info
>
>
> |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X