Hello Alex,
you are using self-signed certificate, which is not secure by default (not
signed by well known authority)
This should be used for testing/development purposes only
You better use some "real" certificate, some of them are available for free
:)
On Sun, Jul 22, 2018 at 5:12 AM Alex
Hello again,
I'm sort of having an issue getting OpenMeetings to run on HTTPS securely.
I followed the instructions on this link:
https://openmeetings.apache.org/RTMPSAndHTTPS.html#_toc_self-signed_certificate
and I was able to run it on port 5443. The problem is that it is not secure
and I'm
Ok problem solved. I'm having a different issue now but I'll make another
post about it.
On Sat, Jul 21, 2018 at 5:39 AM, Alvaro wrote:
> ...downloading the script again
>
>
>
> ..
>
>
>
>
> El sáb, 21-07-2018 a las 11:38 +0200, Alvaro escribió:
>
> Ok, Alex, it
Dear Ludovic and Dan,
The dropdown device list remains blank when the browser cannot connect to the
active device drivers in the OS properly before loading the page.
Solution to this issue:
· Reload the browser.
· Restart the computer.
Better solution: Connect the mic,
Has anyone else seen this behavior?
Use saves whiteboard as a file. But then when he/she tries to reload it
into a whiteboard it won't load. This happened with a MacBook air using Mac
OS 10.9.x
Thanks. Dan
--
Daniel Ascher, M.Ed.
President
A+ Test Prep and Tutoring
"Creating Bright Futures"
I saw the same issue yesterday with someone using a Macbook Air.
On Sat, Jul 21, 2018 at 8:19 AM, Ludovic MESSINGER wrote:
> Hello,
>
> When I open the settings to activate my mwebcam or mic, sometimes the
> device list is blank. For webcam it displays the 1st line and then an other
> blank
Hello,
When I open the settings to activate my mwebcam or mic, sometimes the
device list is blank. For webcam it displays the 1st line and then an
other blank line and for mic the 1st line and then 2 or 3 blank lines.
I have seen this on Chrome with OpenMeetings Version 4.0.3.
It seems
...downloading the script again
..
El sáb, 21-07-2018 a las 11:38 +0200, Alvaro escribió:
> Ok, Alex, it is solved.
> It was a git x265 version question, as told you.
> Please, now you can use the script newly.
> Alvaro
>
>
Ok, Alex, it is solved.
It was a git x265 version question, as told you.
Please, now you can use the script newly.
Alvaro
El sáb, 21-07-2018 a las 10:43 +0200, Alvaro escribió:
> No Alex, 've dont change anything in the script. But is
No Alex, 've dont change anything in the script. But is truththat
yesterday works right and today not.
Must be changed something in the git.Now am working about it.
Will tell you when get the solution.
Alvaro
..
El sáb, 21-07-2018 a las 02:59 -0400, Alex Nyamweya
...Ok, Maxim, For me this loop discussion is finished.
Thanks anyway
Alvaro
El sáb, 21-07-2018 a las 14:11 +0700, Maxim Solodovnik escribió:
> ...For what complicate to newbies about PATH?
>
> ...Simply with my two commands added in the script
> "ffmpeg_centos7.sh"
>
> I believe for newbies
I decided to reinstall the OS once again.
On Sat, Jul 21, 2018 at 12:59 AM, Maxim Solodovnik
wrote:
> Is it accessible at same machine? (using `localhost` instead of
> `my-ip-address`)
> On Fri, Jul 20, 2018 at 9:24 PM Alex Nyamweya
> wrote:
> >
> > On my phone I'm getting the address not
...For what complicate to newbies about PATH?
...Simply with my two commands added in the script "ffmpeg_centos7.sh"
I believe for newbies it is the same :)
I have modified script as follows:
cp /root/bin/nasm /usr/bin
cp /root/bin/yasm /usr/bin
Instead of adding above 2 lines, you can add
Hello,
Did you change the script again? Now when I try running ffmpeg_centos7.sh
according to the installation instructions. It's not creating the ffmpeg
file.
ERROR: x265 not found using pkg-config
If you think configure made a mistake, make sure you are using the latest
version from Git. If
...and come back again to:
...For what complicate to newbies about PATH?...Simply with my two
commands added in the script "ffmpeg_centos7.sh"and in the ffmpeg web
page, it are the same, there is no error compilation.
.
El sáb, 21-07-2018 a las 13:28 +0700, Maxim Solodovnik
I this case the PATH variable set incorrectly :(
these 2 entries `/home/guadal/.local/bin:/home/guadal/bin`
should be replaced with `/root/.local/bin:/root/bin`
I would update PATH instead of copiing files into /usr/bin
It will make clean-up much easier :)
On Sat, Jul 21, 2018 at 1:15 PM
...Maxim, use your imagination.So is better for you?:
[root@tosa guadal]# echo
$PATH/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/home/guada
l/.local/bin:/home/guadal/bin
I don't build as 'guadal', i build as root.Please, take a look the
attached picture.
17 matches
Mail list logo