Which is the best open source ecommerce platform?

[Turritopsis Dohrnii Teo En Ming]

Good afternoon from Singapore,


There are far too many choices when it comes to open source ecommerce solutions.


Are there any credible rankings of open source ecommerce platforms?


Which open source ecommerce solution do you think is the best and tell me why.


Thank you.



===BEGIN SIGNATURE===

Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 30 Oct 2017

[1] https://tdtemcerts.wordpress.com/

[2] http://tdtemcerts.blogspot.sg/

[3] 
https://www.scribd.com/user/270125049/Teo-En-Ming

===END SIGNATURE===
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Network Manager not Retaining Wifi Password

[Stephen Morris]

On 14/9/18 12:29 am, Ed Greshko wrote:

On 9/13/18 7:39 PM, Stephen Morris wrote:

After the last system update in F28 Network Manager is not retaining the wifi
password entered into its security tab. When I enter the password and select 
apply
then 'OK' to exit network manager, when I get back in the password is gone. Is
anyone else seeing this issue or have any tips on how to rectify this issue?

Can we assume you're using GNOME?

If so, when you have the security tab open there is what looks like 2 people on 
the
right hand side in the password box.
If you click on that there should be 3 choices.  What is yours set to?


Thanks Ed, sorry its taken me a while to response, I haven't been on 
much recently. I'm actually using KDE. As well as the situation 
mentioned above, when I get into KDE I get prompted for my password to 
supply to Kwallet, and then I get prompted to enter my Wifi password, at 
which point the wifi gets activated and then the firewall get started 
for the network adapter. I was using the option 'Store this password for 
this user only (encrypted)' which was not retaining it on exit, as a 
test I switched to 'Store this password for all users (Unencrypted)' 
which seems to be retaining it from the perspective of when I exit and 
get back in the password is still there. If the 2nd option has indeed 
retained the password, could there be a slight logic error in 
networkmanager where 'Store this password for this user only 
(encrypted)' seems to be functioning like the option of 'Ask for this 
password every time'?



regards,

Steve



___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Network Manager not Retaining Wifi Password

[Ed Greshko]

On 9/26/18 4:34 PM, Stephen Morris wrote:
> On 14/9/18 12:29 am, Ed Greshko wrote:
>> On 9/13/18 7:39 PM, Stephen Morris wrote:
>>> After the last system update in F28 Network Manager is not retaining the 
>>> wifi
>>> password entered into its security tab. When I enter the password and 
>>> select apply
>>> then 'OK' to exit network manager, when I get back in the password is gone. 
>>> Is
>>> anyone else seeing this issue or have any tips on how to rectify this issue?
>> Can we assume you're using GNOME?
>>
>> If so, when you have the security tab open there is what looks like 2 people 
>> on the
>> right hand side in the password box.
>> If you click on that there should be 3 choices.  What is yours set to?
>
> Thanks Ed, sorry its taken me a while to response, I haven't been on much 
> recently.
> I'm actually using KDE. As well as the situation mentioned above, when I get 
> into
> KDE I get prompted for my password to supply to Kwallet, and then I get 
> prompted to
> enter my Wifi password, at which point the wifi gets activated and then the
> firewall get started for the network adapter. I was using the option 'Store 
> this
> password for this user only (encrypted)' which was not retaining it on exit, 
> as a
> test I switched to 'Store this password for all users (Unencrypted)' which 
> seems to
> be retaining it from the perspective of when I exit and get back in the 
> password is
> still there. If the 2nd option has indeed retained the password, could there 
> be a
> slight logic error in networkmanager where 'Store this password for this user 
> only
> (encrypted)' seems to be functioning like the option of 'Ask for this password
> every time'?
>
>
I see.  I am a KDE user as well.

I have my WiFi security set to "Store password for this user only (encrypted)". 
 When
I activate the connection I am prompted for my kwallet password and the
connection is made without asking for the WiFi password.  So, in my case there 
is no
issue.  The WiFi password is being retained.

If you bring up kwalletmanager5 you should see an entry for "Network 
Management". 
This is where WiFi and VPN "secrets" are kept in the Maps area.

Your WiFi connection should have a name.  And that name should (in most cases) 
match
a name in /etc/sysconfig/network-scripts.

For example, one of my WiFi connections is "asus2" and in the network-scripts
directory I have a ifcfg-asus2.  Looking at that file there is a UUID line.
UUID=8eef1e08-095e-4fb2-8dab-50ef1c19a114.  This line matches a line in the 
Maps area
and there exists a "psk" Key.

Do you have something similar?


-- 
Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell
them, then tell them what you told them."



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: fedora cloud AWS randomly shutdown

[Neal Becker]

Rick Stevens wrote:

> On 9/25/18 12:32 PM, Neal Becker wrote:
>> I'm using f28 cloud on AWS as a compute farm.  It seems that instances
>> randomly shutdown within hours of starting.  An example log:
>> 
>> ...
>> Fedora 28 (Cloud Edition)
>> Kernel 4.16.3-301.fc28.x86_64 on an x86_64 (ttyS0)
>> 
>>  Stopping Restore /run/initramfs on shutdown...
>> [  OK  ] Removed slice system-sshd\x2dkeygen.slice.
>>  Stopping User Manager for UID 1000...
>> ...
>> 
>> In this case after about 4 hours it seems to have spontaneously shutdown.
>> This happens with high probability - maybe 2/10 instances I start
>> spontaneously shutdown.
>> 
>> Any ideas what's going on?  I'm just wondering if this is something
>> specific to fedora cloud edition, because it doesn't seem to be a common
>> complaint on AWS (most of which is ubuntu).
> 
> Are you getting emails from AWS that they're shutting down your
> instance? AWS does some testing and, should your instance fail their
> tests, they will shut it down "to protect others sharing the hardware".
> If this is what's happening, you should get an email about it (we get
> one perhaps 20% of the time) and if not, check the AWS admin portal
> under "Events" right after a restart. There should be a record about it.
> That record goes away after a while (not sure how long it hangs around).
> 
> In my experience, AWS is rather vague as to just _what_ tests they use
> to determine if your instance is dangerous so it can be difficult to fix
> your code. We've got some AWS stuff that's been up for well over a year,
> but others they shut down because they fail these mysterious tests.
> 
> If you're using instance store disks, the disk image is purged when you
> restart your instance so your logs probably don't contain why the system
> shut down the last time. The only way to hang onto that stuff is to use
> persistent (EBC) storage for your machine--at least for the logs (I'd
> recommend st1-type storage for logs). Persistent storage at AWS can get
> expensive depending on how big it is, but it may be necessary to sort
> this out. Once figured out, you can get rid of the EBS storage to
> minimize costs.
> 
> This may be a Fedora Cloud issue. It may be something you're doing in an
> application. It may be AWS protecting itself. Hard to tell.

Shutdowns occur with very high probability within few hours.  Like, maybe 
20% of my machines shutdown within a few hours.  I suspect machines with 
high load average shutdown.  But that's not behavior I'd expect from fedora 
workstation!  I'm wondering if there's something about the fedora cloud 
setup causing this?


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

VNC alternatives

[Robert Moskowitz]

It seems Tiger-vncserver is broken WRT polkit for any spin other than 
gnome.  Definitely not Xfce that I use.  The work around is nasty:  
Connect via SSH and run vncserver from the command line. But probably 
can do it better via SCREEN and just forget about that screen session...


So it is time to look at the alternatives.  I know they are out there 
and have been talked about on this list, but my search foo is weak (as 
always).  So can I have a bit of help in figuring out what to replace my 
decades-old connection to VNC?


thanks
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: VNC alternatives

[Tom Horsley]

On Wed, 26 Sep 2018 10:25:45 -0400
Robert Moskowitz wrote:

> So can I have a bit of help in figuring out what to replace my 
> decades-old connection to VNC?

I use x2go, but it operates in a completely different fashion
from VNC (and I don't think it can allow you to share the
physical screen, it is always a separate X session).
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: fedora cloud AWS randomly shutdown

[Rick Stevens]

On 9/26/18 5:03 AM, Neal Becker wrote:
> Rick Stevens wrote:
> 
>> On 9/25/18 12:32 PM, Neal Becker wrote:
>>> I'm using f28 cloud on AWS as a compute farm.  It seems that instances
>>> randomly shutdown within hours of starting.  An example log:
>>>
>>> ...
>>> Fedora 28 (Cloud Edition)
>>> Kernel 4.16.3-301.fc28.x86_64 on an x86_64 (ttyS0)
>>>
>>>  Stopping Restore /run/initramfs on shutdown...
>>> [  OK  ] Removed slice system-sshd\x2dkeygen.slice.
>>>  Stopping User Manager for UID 1000...
>>> ...
>>>
>>> In this case after about 4 hours it seems to have spontaneously shutdown.
>>> This happens with high probability - maybe 2/10 instances I start
>>> spontaneously shutdown.
>>>
>>> Any ideas what's going on?  I'm just wondering if this is something
>>> specific to fedora cloud edition, because it doesn't seem to be a common
>>> complaint on AWS (most of which is ubuntu).
>>
>> Are you getting emails from AWS that they're shutting down your
>> instance? AWS does some testing and, should your instance fail their
>> tests, they will shut it down "to protect others sharing the hardware".
>> If this is what's happening, you should get an email about it (we get
>> one perhaps 20% of the time) and if not, check the AWS admin portal
>> under "Events" right after a restart. There should be a record about it.
>> That record goes away after a while (not sure how long it hangs around).
>>
>> In my experience, AWS is rather vague as to just _what_ tests they use
>> to determine if your instance is dangerous so it can be difficult to fix
>> your code. We've got some AWS stuff that's been up for well over a year,
>> but others they shut down because they fail these mysterious tests.
>>
>> If you're using instance store disks, the disk image is purged when you
>> restart your instance so your logs probably don't contain why the system
>> shut down the last time. The only way to hang onto that stuff is to use
>> persistent (EBC) storage for your machine--at least for the logs (I'd
>> recommend st1-type storage for logs). Persistent storage at AWS can get
>> expensive depending on how big it is, but it may be necessary to sort
>> this out. Once figured out, you can get rid of the EBS storage to
>> minimize costs.
>>
>> This may be a Fedora Cloud issue. It may be something you're doing in an
>> application. It may be AWS protecting itself. Hard to tell.
> 
> Shutdowns occur with very high probability within few hours.  Like, maybe 
> 20% of my machines shutdown within a few hours.  I suspect machines with 
> high load average shutdown.  But that's not behavior I'd expect from fedora 
> workstation!  I'm wondering if there's something about the fedora cloud 
> setup causing this?

Please check the AWS portal and see if they're killing your machines or
if they're shutting down of their own accord. And as I said before,
you may need to set up an EBC st1 storage volume and mount it at
/var/log to persist logs across reboots so you can examine them when you
bring the machine back up.

It might an idea to set up a small AWS instance with the EBC storage at
/var/log as a log server and have all your other instances log to it.
You'd be able to capture any of your AWS instance logs that way on a
single EBC storage volume.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
- Politicians are the opposite of pickpockets because you never see  -
-them take their hand out of your pocket.-
- -- Larry Fine  -
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: VNC alternatives

[Robert Moskowitz]

On 9/26/18 12:43 PM, Tom Horsley wrote:

On Wed, 26 Sep 2018 10:25:45 -0400
Robert Moskowitz wrote:


So can I have a bit of help in figuring out what to replace my
decades-old connection to VNC?

I use x2go, but it operates in a completely different fashion
from VNC (and I don't think it can allow you to share the
physical screen, it is always a separate X session).

I just got a private message on using rc.local that looks a lot like 
what others have hacked at connecting with ssh to start vncserver and 
avoid the polkit problem that systemd seems to make.  So I am going to 
give this a try first before abandoning ship




___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Can't get to https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/

[Danesh Manoharan]

guys, need some advise. I'm unable to access 
https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/
 from my organization's network. Outside the network is fine. The 
network/security team has confirmed that the url has been white listed. Who can 
I contact to verify we are not on your blacklist?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: VNC alternatives

[ToddAndMargo]

On 9/26/18 7:25 AM, Robert Moskowitz wrote:
It seems Tiger-vncserver is broken WRT polkit for any spin other than 
gnome.  Definitely not Xfce that I use.  The work around is nasty: 
Connect via SSH and run vncserver from the command line. But probably 
can do it better via SCREEN and just forget about that screen session...


So it is time to look at the alternatives.  I know they are out there 
and have been talked about on this list, but my search foo is weak (as 
always).  So can I have a bit of help in figuring out what to replace my 
decades-old connection to VNC?


thanks



I use XRDP a lot.   It's downfall or upside however you want
to look at it, is that it opens a separate session to the remote
viewer, meaning you can't assist someone at the other end
and the other end can't see what you are doing ("You pay who
how much more than me").

For clients, I use  xfreerdp on Linux and mstsc on Windows



___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: VNC alternatives

[Ed Greshko]

On 9/26/18 10:25 PM, Robert Moskowitz wrote:
> It seems Tiger-vncserver is broken WRT polkit for any spin other than gnome. 
> Definitely not Xfce that I use.  The work around is nasty:  Connect via SSH 
> and run
> vncserver from the command line. But probably can do it better via SCREEN and 
> just
> forget about that screen session...
>
> So it is time to look at the alternatives.  I know they are out there and 
> have been
> talked about on this list, but my search foo is weak (as always).  So can I 
> have a
> bit of help in figuring out what to replace my decades-old connection to VNC?

As discussed on the test list, the actual problem with tiger vncserver and 
polkit
arises when it is started via the supplied vncserver@.service systemd file.
If started manually that problem doesn't exist. 

Just like in all things Linux, there are multiple ways to accomplish having the
server manually started.

1.  Manually ssh into the remote system and start the server before starting 
your client.

2.  Use a vnc-client such as remmina which has a "pre" and "post" command that 
will
automate #1 above.

3.  Use the rc.local method you mentioned in another post to start the server 
at boot
time.

4.  Use a custom vncserver.service file such as the one I pointed you to on the 
test
list.  The advantage of this over #3 is that it stays in the systemd
framework and can easily "enabled", "disabled", "stopped", and "started".  It is
really no more "ugly a hack" as the rc.local route. 

The "problem" with seeking alternatives is that you'd have to "lean new tricks" 
and
may run into new things you'll have to get used to or workaround.
While that can be "fun" it seems to me (just an opinion) invoking an alternate 
method
of starting the server provides you with less changes to deal with.

-- 
Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell
them, then tell them what you told them."



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Can't get to https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/

[Joe Zeff]

On 09/26/2018 01:54 PM, Danesh Manoharan wrote:

guys, need some advise. I'm unable to 
accesshttps://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/
  from my organization's network. Outside the network is fine. The 
network/security team has confirmed that the url has been white listed. Who can 
I contact to verify we are not on your blacklist?


Two questions: first, have you tried pinging 
copr-be.cloud.fedoraproject.org to make sure it's reachable from your 
network and second, what does your browser report as the reason it 
couldn't display the page?

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: VNC alternatives

[Robert Moskowitz]

On 9/26/18 4:37 PM, Ed Greshko wrote:

On 9/26/18 10:25 PM, Robert Moskowitz wrote:

It seems Tiger-vncserver is broken WRT polkit for any spin other than gnome.
Definitely not Xfce that I use.  The work around is nasty:  Connect via SSH and 
run
vncserver from the command line. But probably can do it better via SCREEN and 
just
forget about that screen session...

So it is time to look at the alternatives.  I know they are out there and have 
been
talked about on this list, but my search foo is weak (as always).  So can I 
have a
bit of help in figuring out what to replace my decades-old connection to VNC?

As discussed on the test list, the actual problem with tiger vncserver and 
polkit
arises when it is started via the supplied vncserver@.service systemd file.
If started manually that problem doesn't exist.

Just like in all things Linux, there are multiple ways to accomplish having the
server manually started.

1.  Manually ssh into the remote system and start the server before starting 
your client.

2.  Use a vnc-client such as remmina which has a "pre" and "post" command that 
will
automate #1 above.

3.  Use the rc.local method you mentioned in another post to start the server 
at boot
time.


Yes.  I am getting mixed personal feelings about stepping back to SysV 
approach.  I realize I still have a ClearOS6 system running that uses 
SysV for me to look at, but still.  Got to move forward. I really tried 
to embrace Systemd when it came out.




4.  Use a custom vncserver.service file such as the one I pointed you to on the 
test
list.  The advantage of this over #3 is that it stays in the systemd
framework and can easily "enabled", "disabled", "stopped", and "started".  It is
really no more "ugly a hack" as the rc.local route.


For others here the one Ed and I are talking about is:

https://forums.fedoraforum.org/showthread.php?316905-PolicyKit-failed-over-headless-VNC&p=1809280#post1809280

I have to study this more to get the 'feel' of it and what exactly the 
setup steps are.


The "problem" with seeking alternatives is that you'd have to "lean new tricks" 
and
may run into new things you'll have to get used to or workaround.
While that can be "fun" it seems to me (just an opinion) invoking an alternate 
method
of starting the server provides you with less changes to deal with.


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Can't get to https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/

[Danesh Manoharan]

1. pings don't come back. Think icmp is turned off.
2. On a machine inside.
[root@testmachine001 ~] #wget  
https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/
--2018-09-26 21:34:23--  (try:20)  
https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/
Connecting to copr-be.cloud.fedoraproject.org|209.132.184.48|:443... failed: 
Connection timed out.
Giving up.
3. On a machine outside.
[root@testmachine ~]# wget 
https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/
--2018-09-27 06:25:26--  
https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/
Resolving copr-be.cloud.fedoraproject.org... 209.132.184.48
Connecting to copr-be.cloud.fedoraproject.org|209.132.184.48|:443... connected.
ERROR: certificate common name “copr.fedorainfracloud.org” doesn’t match 
requested host name “copr-be.cloud.fedoraproject.org”.
To connect to copr-be.cloud.fedoraproject.org insecurely, use 
‘--no-check-certificate’.

I suspect we might have gotten blacklisted, maybe? We've been running a large 
lustre install with IML which tells it's hosts to pull from the repo.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Can't get to https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/

[Samuel Sieb]

On 9/26/18 3:30 PM, Danesh Manoharan wrote:

3. On a machine outside.
[root@testmachine ~]# wget 
https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/
--2018-09-27 06:25:26--  
https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/
Resolving copr-be.cloud.fedoraproject.org... 209.132.184.48
Connecting to copr-be.cloud.fedoraproject.org|209.132.184.48|:443... connected.
ERROR: certificate common name “copr.fedorainfracloud.org” doesn’t match 
requested host name “copr-be.cloud.fedoraproject.org”.
To connect to copr-be.cloud.fedoraproject.org insecurely, use 
‘--no-check-certificate’.


This might be a problem.  If your work uses a proxy, it might block 
something like this.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Can't get to https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/

[Ed Greshko]

On 9/27/18 7:22 AM, Samuel Sieb wrote:
> On 9/26/18 3:30 PM, Danesh Manoharan wrote:
>> 3. On a machine outside.
>> [root@testmachine ~]# wget
>> https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/
>> --2018-09-27 06:25:26-- 
>> https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/
>> Resolving copr-be.cloud.fedoraproject.org... 209.132.184.48
>> Connecting to copr-be.cloud.fedoraproject.org|209.132.184.48|:443... 
>> connected.
>> ERROR: certificate common name “copr.fedorainfracloud.org” doesn’t match 
>> requested
>> host name “copr-be.cloud.fedoraproject.org”.
>> To connect to copr-be.cloud.fedoraproject.org insecurely, use
>> ‘--no-check-certificate’.
>
> This might be a problem.  If your work uses a proxy, it might block something 
> like
> this.

Well, he said "On a machine outside" which I took to mean not in the office.

FWIW,

[egreshko@meimei tmp]$ wget
https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/
--2018-09-27 07:24:19-- 
https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/
Resolving copr-be.cloud.fedoraproject.org (copr-be.cloud.fedoraproject.org)...
209.132.184.48
Connecting to copr-be.cloud.fedoraproject.org
(copr-be.cloud.fedoraproject.org)|209.132.184.48|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 75982 (74K) [text/html]
Saving to: ‘index.html’

index.html   100%[=>]  74.20K   458KB/s    in 0.2s  
 

2018-09-27 07:24:20 (458 KB/s) - ‘index.html’ saved [75982/75982]

Just to be complete I would also do

telnet 209.132.184.48 443    as well as
telnet copr-be.cloud.fedoraproject.org 443

Both at work and outside of work.

-- 
Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell
them, then tell them what you told them."



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Can't get to https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/

[Joe Zeff]

On 09/26/2018 04:30 PM, Danesh Manoharan wrote:

1. pings don't come back. Think icmp is turned off.


Try traceroute, to see how far the pings get before they die.  It's 
unlikely, but there might be some server you're going through that's 
blocking the pings.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: VNCserver seems to be working - Re: VNC alternatives

[Ed Greshko]

On 9/27/18 9:28 AM, Robert Moskowitz wrote:
> Per the instructions from the Fedoraforum.  Took a bit, but I am mounting USB
> drive.  Polkit is prompting me for my password and that lets me mount the 
> drive. 
> Probably because I am in group wheel.
>
> So call is off for alternative to vnc and to remember how to do it with SysV. 
>  I am
> staying with Systemd, but
>
> What a MESS!

FWIW, I use "remmina" as my VNC client.  I also use public key authentication 
for
ssh.  So, with remmina I simply put

ssh egreshko@192.168.1.80 vncserver as a "pre-command" to start the 
vncserver and
ssh egreshko@192.168.1.80 vncserver -kill :1   as a "post-command" to stop the 
vncserver

For me this is an optimal solution since I can just, basically, use copy/paste 
into
the various profiles for all the test systems that I
tend to create and destroy frequently.  This way I don't need to fuss and muss 
with
making changes to systemd files to get this working.
Basically, it saves me time, keystrokes, and use of my memory.  :-)

-- 
Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell
them, then tell them what you told them."



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Can't get to https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/

[Samuel Sieb]

On 9/26/18 4:29 PM, Ed Greshko wrote:

On 9/27/18 7:22 AM, Samuel Sieb wrote:

On 9/26/18 3:30 PM, Danesh Manoharan wrote:

3. On a machine outside.
[root@testmachine ~]# wget
https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/
--2018-09-27 06:25:26--
https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/
Resolving copr-be.cloud.fedoraproject.org... 209.132.184.48
Connecting to copr-be.cloud.fedoraproject.org|209.132.184.48|:443... connected.
ERROR: certificate common name “copr.fedorainfracloud.org” doesn’t match 
requested
host name “copr-be.cloud.fedoraproject.org”.
To connect to copr-be.cloud.fedoraproject.org insecurely, use
‘--no-check-certificate’.


This might be a problem.  If your work uses a proxy, it might block something 
like
this.


Well, he said "On a machine outside" which I took to mean not in the office.


Yes, that was my point.  It worked outside, but gave a certificate 
warning.  If they have a proxy like where I work and it detects that, it 
might completely block the connection.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Can't get to https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/

[Ed Greshko]

On 9/27/18 10:03 AM, Samuel Sieb wrote:
> On 9/26/18 4:29 PM, Ed Greshko wrote:
>> On 9/27/18 7:22 AM, Samuel Sieb wrote:
>>> On 9/26/18 3:30 PM, Danesh Manoharan wrote:
 3. On a machine outside.
 [root@testmachine ~]# wget
 https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/

 --2018-09-27 06:25:26--
 https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/

 Resolving copr-be.cloud.fedoraproject.org... 209.132.184.48
 Connecting to copr-be.cloud.fedoraproject.org|209.132.184.48|:443... 
 connected.
 ERROR: certificate common name “copr.fedorainfracloud.org” doesn’t match 
 requested
 host name “copr-be.cloud.fedoraproject.org”.
 To connect to copr-be.cloud.fedoraproject.org insecurely, use
 ‘--no-check-certificate’.
>>>
>>> This might be a problem.  If your work uses a proxy, it might block 
>>> something like
>>> this.
>>
>> Well, he said "On a machine outside" which I took to mean not in the office.
>
> Yes, that was my point.  It worked outside, but gave a certificate warning.  
> If
> they have a proxy like where I work and it detects that, it might completely 
> block
> the connection.
>

I see your point.  I suppose I was confused since, like I showed, I am certainly
outside of his company (or any other) and I don't get a "certificate warning".
So, I am left to wonder why he gets one and I don't. 


-- 
Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell
them, then tell them what you told them."



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Can't get to https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-for-lustre/epel-7-x86_64/

[Todd Zullinger]

Danesh Manoharan wrote:
> I suspect we might have gotten blacklisted, maybe? We've
> been running a large lustre install with IML which tells
> it's hosts to pull from the repo.

I would try asking in #fedora-buildsys on irc.freenode.net
or send a message to the copr mailing list at
copr-de...@lists.fedorahosted.org.

I have seen someone else whose IP's were blacklisted by the
copr systems recently, so that's certinly a possiblity.

-- 
Todd
~~
If everything seems to be going well, you have obviously overlooked
something.



signature.asc
Description: PGP signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org