fred-users

fred-users@lists.nic.cz

1 participants
408 discussions

by Jaromir Talir

Hi, after some time we are announcing a new version of FRED. As usually release notes are published here: https://fred.nic.cz/documentation/html/ReleaseNotes/ We have intentionally not announced version 2.37 since this version was changing hardcoded default for WHOIS disclose flags from "everything is by default public" to "everything is by default hidden" of course because of GDPR. New default was again hardcoded and immediate upgrade could cause issue to registrars that relies on default policy. With version 2.38 this default policy is configuration option so registry has control when this policy change based on discussion with registrars. All the information should be seen from documentation. I'd like to pick one change from release notes to write about little bit more and this is handling incoming payments. We are trying to make FRED even more modular and move all about payments and invoices into separated module. There is background idea that at some point in time, this module could be replaced with generic accounting software that will take care of issuing invoices which should not be responsibility of registry. For now, the only visible change is that tab payments disappears from web administration interface (Daphne) and also associated database tables bank_payment and bank_statement are not required. My assumption is that this change doesn't have effect for any instance but in case it has, there is a new component called Pain (from "payments and invoices") that provides the same functionality but needs to be installed as additional thing. Feel free to ask more about this if you'd like to try it. Regards, Jaromir -- Jaromir Talir Technicky partner / Technical Fellow ------------------------------------------- CZ.NIC, z.s.p.o. -- .cz domain registry Milesovska 5, 130 00 Praha 3, Czech Republic mailto:jaromir.talir@nic.cz http://nic.cz/ sip:jaromir.talir@nic.cz tel:+420.222745107 mob:+420.739632712 fax:+420.222745112 -------------------------------------------

6 let, 11 měsíců

Error: CORBA NameService not running

by Moeketsi Maphoi

Greetings, I have a fresh install of FRED 2.35.0 on Ubuntu Server 16.04 LTS but the services can't seem to start, only fred-pyfred is active. The ExecStart commands like: /usr/sbin/fred-rifd -ORBendPoint giop:tcp::2224 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-rifd.conf exit with failure of Error: CORBA NameService not running. /usr/sbin/fred-adifd -ORBendPoint giop:tcp::2222 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-adifd.conf exit with failure of Error: CORBA NameService not running. /usr/sbin/fred-pifd -ORBendPoint giop:tcp::2223 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-pifd.conf exit with failure of Error: CORBA NameService not running. /usr/sbin/fred-logd -ORBendPoint giop:tcp::2226 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-logd.conf exit with failure of Error: CORBA NameService not running. /usr/sbin/fred-msgd -ORBendPoint giop:tcp::2228 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-msgd.conf exit with failure of Error: CORBA NameService not running. /usr/sbin/fred-rsifd -ORBendPoint giop:tcp::2234 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-rsifd.conf exit with failure of Error: CORBA NameService not running. The fred-webadmin log when running /usr/bin/fred-webadmin is as follows: omniORB: (0) 2019-01-16 08:03:11.886060: ERROR! omniORBpy version 4.2 expects stubs version 4.2. Stubs in /usr/lib/python2.7/dist-packages/CosNaming_idl.pyc are version 3.0 (rev 0). Traceback (most recent call last): File "/usr/bin/fred-webadmin", line 8, in <module> from fred_webadmin.controller import adif File "/usr/lib/python2.7/dist-packages/fred_webadmin/controller/adif.py", line 38, in <module> import fred_webadmin.auth.corba_auth as auth File "/usr/lib/python2.7/dist-packages/fred_webadmin/auth/corba_auth.py", line 1, in <module> import fred_webadmin.corbarecoder as recoder File "/usr/lib/python2.7/dist-packages/fred_webadmin/corbarecoder.py", line 5, in <module> from pyfco.recoder import decode_iso_date, decode_iso_datetime, encode_iso_date, encode_iso_datetime File "/usr/lib/python2.7/dist-packages/pyfco/__init__.py", line 3, in <module> from .name_service import CorbaNameServiceClient File "/usr/lib/python2.7/dist-packages/pyfco/name_service.py", line 6, in <module> import CosNaming File "/usr/lib/python2.7/dist-packages/CosNaming/__init__.py", line 9, in <module> import CosNaming_idl File "/usr/lib/python2.7/dist-packages/CosNaming_idl.py", line 7, in <module> _omnipy.checkVersion(3,0, __file__) ImportError: Stubs not compatible with omniORBpy version 4.2. Is there a way I can solve this compatibility issure? The process omniorb4-nameserver status output is as follows: omniorb4-nameserver.service - LSB: Start the omniNames Interoperable Naming Service Loaded: loaded (/etc/init.d/omniorb4-nameserver; bad; vendor preset: enabled) Active: active (exited) since Wed 2019-01-16 07:39:02 SAST; 11min ago Docs: man:systemd-sysv-generator(8) Process: 28050 ExecStop=/etc/init.d/omniorb4-nameserver stop (code=exited, status=0/SUCCESS) Process: 28133 ExecStart=/etc/init.d/omniorb4-nameserver start (code=exited, status=0/SUCCESS) Tasks: 0 Memory: 0B CPU: 0 Jan 16 07:39:02 fred-test systemd[1]: Starting LSB: Start the omniNames Interoperable Naming Service... Jan 16 07:39:02 fred-test omniorb4-nameserver[28133]: * Starting omniORB name server omniNames Jan 16 07:39:02 fred-test omniorb4-nameserver[28133]: ...done. Jan 16 07:39:02 fred-test systemd[1]: Started LSB: Start the omniNames Interoperable Naming Service. In fred-eppd.log I found [sessionID 216968] Could not obtain object reference for alias 'EPP_alias'. Check mod_corba's configuration, whoever the module does seem to be enables under apache mods-enabled. What could be the problem? Regards, Moeketsi Maphoi

7 let

Fedora 29 packages not available.

by Jóhann B. Guðmundsson

Greetings Fedora 29 got officially released on 30 October last year but no packages have been built for that release [1] as of today hence installation on the distro fails with.... Failed to synchronize cache for repo 'fred', ignoring this repo. No match for argument: fred-* Any particular reason the components have not been built for the 29 release of Fedora? Regards Jóhann B. 1. http://archive.nic.cz/yum/fred/fedora/

7 let

Cannot hide address fields in the contact create command

by Kuchta, Jiri

Hello, I have noticed there is an option to set address fields disclosure settings in the contact update command, but there is no such option in the create command. Is there some reason for the commands to have different disclosure options? Best regards, Jiri Kuchta Je dobré vědět, že tento e-mail a přílohy jsou důvěrné. Pokud spolu jednáme o uzavření obchodu, vyhrazujeme si právo naše jednání kdykoli ukončit. Pro fanoušky právní mluvy - vylučujeme tím ustanovení občanského zákoníku o předsmluvní odpovědnosti. Pravidla o tom, kdo u nás a jak vystupuje za společnost a kdo může co a jak podepsat naleznete zde<https://onas.seznam.cz/cz/podpisovy-rad-cz.html> You should know that this e-mail and its attachments are confidential. If we are negotiating on the conclusion of a transaction, we reserve the right to terminate the negotiations at any time. For fans of legalese-we hereby exclude the provisions of the Civil Code on pre-contractual liability. The rules about who and how may act for the company and what are the signing procedures can be found here<https://onas.seznam.cz/cz/signature-rules.html>.

7 let, 2 měsíce

ERROR: Backend server is not running!

by Moeketsi Maphoi

Greetings, I am experiencing a bit of a problem here on daphne, out of nowhere. The FRED services have never stopped running for two months now but daphne puts out the following message after hitting login. Error: Error: Backend server is not running! Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/fred_webadmin/exposed.py", line 25, in _wrapper return view_func(*args, **kwd) File "/usr/lib/python2.7/dist-packages/fred_webadmin/controller/adif.py", line 241, in login self._authenticate(form, admin) File "/usr/lib/python2.7/dist-packages/fred_webadmin/controller/adif.py", line 175, in _authenticate auth.authenticate_user(admin, login, password) File "/usr/lib/python2.7/dist-packages/fred_webadmin/auth/corba_auth.py", line 11, in authenticate_user admin.authenticateUser(recoder.u2c(username), recoder.u2c(password)) File "/tmp/tmprSxSnq", line 6903, in authenticateUser TRANSIENT: CORBA.TRANSIENT(omniORB.TRANSIENT_ConnectFailed, CORBA.COMPLETED_NO) All FRED services are still running. The logs don't show anything conclusive, what could be happening? Regards, Moeketsi Maphoi Systems Engineer: LsNIC

7 let, 2 měsíce

Fwd: An apparent problem with web-admin

by Mario Guerra

Hello. When trying to unblock a domain using Webadmin it does not show the Unblock button in despite it is blocked. I'm showing this problem in this attachment. Have any of you experienced this?. We are using FRED 2.36 under Ubuntu 16.04. Any other means of unblocking the domain? Best Mario Guerra

7 let, 3 měsíce

problem registrar EPP connection - timeout - ERROR: socket.sslerror: _ssl.c:477

by Dr P Nyirenda

One of our registrars is facing a problem making an EPP connection to our .mw registry running FRED. The connection sometimes succeeds and sometime it fails with "ERROR: socket.sslerror: _ssl.c:477" - on a random on-and-off scenario that seems rather random, we cannot tell when it will fail or succeed. After many observations, I requested the registrar to install fred-client so that I can also test the connection from their end. Sessions look like the ones copied here below where one session was successful to conned and the other one failed. I have looked at this in detail and I need help to check what is really going on. I have now done a TCPDUMP of these connections and the result is copied as here attached, one for a successful connection and one for a failed connection. You will see that in the failed connection TCPDUMP shows that the fred-client on 88.208.201.35 was talking to the FRED server on 196.45.190.7 but the fred-client appears to stop listening even though the FRED server makes a few more attempts to the fred-client. The registrar is experiencing the same for their own client, it sometimes connects successfully and sometimes fails with no predictable pattern. My logs including those on DAPHNE show that most other registrars are connecting ok with no such problems. Can you help check what the problem could be with this one registrar? Is there another log that I can check to see what exactly is causing these connections to fail? Regards, Paulos ====================== Dr Paulos B Nyirenda NIC.MW & .mw ccTLD http://www.registrar.mw [######## successful connection #############] paulos@ndovu [~/fred-client-2.8.0]# ./fred-client Czech translation not available FredClient PACKAGE_VERSION Type "help", "license" or "credits" for more information. Using configuration from conf/fred-client.conf Connecting to ngoli.sdnp.org.mw, port 700 ... Connected! AFRIREGISTER-REG(a)ngoli.sdnp.org.mw> quit Logout command sent to server Ending session at ngoli.sdnp.org.mw Disconnected. [######## failed connection #############] paulos@ndovu [~/fred-client-2.8.0]# ./fred-client Czech translation not available FredClient PACKAGE_VERSION Type "help", "license" or "credits" for more information. Using configuration from conf/fred-client.conf Connecting to ngoli.sdnp.org.mw, port 700 ... ERROR: socket.sslerror: _ssl.c:477: The handshake operation timed out (ngoli.sdnp.org.mw:700) paulos@ndovu [~/fred-client-2.8.0]# --- This email has been checked for viruses by AVG. https://www.avg.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. The following section of this message contains a file attachment prepared for transmission using the Internet MIME message format. If you are using Pegasus Mail, or any other MIME-compliant system, you should be able to save it or view it from within your mailer. If you cannot, please ask your system administrator for assistance. ---- File information ----------- File: afriregister-reg-tcpdump-ok-and-failed-EPP-connection-25-7-18.txt Date: 25 Jul 2018, 15:09 Size: 8110 bytes. Type: Text

7 let, 6 měsíců

HELP with Java and use of SSL private key and digital certificates

by Dr P Nyirenda

Good morning, I have a new registrar that is trying to use Java for EPP connections to our .mw FRED server and they are having a problem on how to use SSL digital keys and SSL certificates in their Java EPP client They want to import the SSL private key and digital certificate into their Java EPP client. . The e-mail address of the registrar is domain(a)idcicp.com and their skype IP is slowturtlej . As of now they are trying something like the following: openssl pkcs12 -export -clcerts -in topnets.cert.pem -inkey topnets.key.pem -out clientuser.p12 keytool -importkeystore -srckeystore clientuser1p12 -srcstoretype PKCS12 -deststoretype JKS -destkeystore ServerKeystore.jks Let me know if you can help and please, if you can, also communicate to them direcly on the above address and skype ID. Regards, Paulos ====================== Dr Paulos B Nyirenda NIC.MW & .mw ccTLD http://www.registrar.mw ------- End of forwarded message ------- --- This email has been checked for viruses by AVG. https://www.avg.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

7 let, 6 měsíců

help how to toggle FRED "serverInzoneManual - The domain is administratively kept in zone"

by Dr P Nyirenda

Help, One of our staff has changed the status of a domain "Set inZone Status" to keep the domain "administratively kept in the zone" on our FRED registry for .mw Daphne is hence showing "serverInzoneManual - The domain is administratively kept in zone" Is there any way to toggle the state of the domain back to its normal status? Can it be done in the database or by sql command? Paulos ============================== Dr Paulos Nyirenda Malawi SDNP Coodinator ---------------------------------------------------------- --- This email has been checked for viruses by AVG. http://www.avg.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

7 let, 9 měsíců

SDNP 2nd .MW Registrars Training Workshop on 24 April 2018 at the Raylls Protea Hotel, Blantyre, Malawi

by Dr P Nyirenda

As you can see here below, in a few weeks we will be running our 2nd workshop for registrars and I am looking for ideas on how to grow our community of registrars. The few registrars that we have so far are having a tough time developing a registrar platform for EPP connections to FRED registry. So, I would like to learn from you on how you have grown your registrars, especially on assisting them technically to do EPP connections. Do you have any comments on our workshop agenda? Do you have a portal for registrars? Do you give them fred-client? Is there a registrar that has developed their own EPP client to connect to FRED and who is willing to share development or source for such a client? Please educate me ! We would be delighted if you could come to Malawi for the one day workshop? Regards, Paulos 2nd WORKSHOP ON .MW DOMAIN REGISTRARS SDNP, the .mw domains registry operator, will run the 2nd .MW Registrars Training Workshop on 24 April 2018 at the Raylls Protea Hotel, Blantyre, Malawi. More details on the workshop are available at SDNP registrar website at http://www.registrar.mw/registrars.php The aim of the workshop is to assist to develop, train and support a sustainable crop of Internet domain registrars in Malawi that do sustainable business on the viable Malawi .mw Country Code Top Level Domain, the .mw ccTLD, using a top of the range domain EPP registry platform. A detailed agenda has been developed for the workshop and a brief version is shown here below with more details available on the above website. Please do let us know if there is any particular topic that you would like to be covered or emphasized. The workshop is open to anyone interested but is particularly targeting registrars and potential registrars. Those interested should register by 19 April 2018. Registration form is available on the above website. There is limited space for 25 participants. We, therefore, cordially invite you to the workshop to learn, share knowledge and network with registrars in Malawi. As in the first workshop we have interest from registrars from abroad who also want to learn and to assist to share expertise and experience on how to develop and sustain a profitable registrar operation and industry in a place like Malawi. The workshop fee to assist to cover the venue is MK25,000 for accredited registrars and MK45,000 for those not yet accredited. Please pay in advance when you register to Malawi SDNP bank account number 674257 National Bank of Malawi, Chichiri Branch. Please bring a laptop for the hands-on exercises. Those who attended the first workshop are also welcome to share their experience or ask specific questions at this workshop so as to further develop their registrar business and operations. TIME TOPIC AREAS 08:00 - 08:30 Workshop Registration, verification 08:30 - 09:00 Workshop opening Session 1 9:00 - 10:00 Overview: Domains, DNS, Registries, Registrars and Registrants Overview, Domains names, TLDs, Internet services, Users, Registrants, Registrars, Registries, How DNS works, WHOIS, framework Session 2 10:30 - 11:00 Becoming a .mw registrar What is a Registrar? Registrants, Registries, 2R, 3R, cases in Africa and globally, overview on EPP - Extensible Provisioning Protocol and its command groups Session 3 11:00 - 11:30 Policy Framework for .mw domains Principles, Domain Registration Policy - Registrar Accreditation - Fees and Charges - Registrant Agreement Session 4 11:30 - 12:30 How to grow the domain name industry in Malawi Domain names and registrar business in Malawi - Example of a successful registrar - presentations from EvMak(TZ), Afriregister(BI), Lexsynergy(UK), ZACR(RSA) - ICANN accreditation - Marketing .mw TLD, Registrar associations LUNCH Session 5 13:30 - 14:00 Registry and DNS operations Global DNS system and operation - BIND and other DNS servers - DNS zones and zone files - FRED Registry and Automatic Zone Generation - DNS propagation Session 6 14:00 - 15:00 Conducting EPP connections - Registry / Server Side Requirements for registering a domain on .mw registry, Contacts, handles, nssets, DNS servers, data validation, WHOIS - Requirements for a registrar to connect to .mw registry, Registrar Handle, Username and EPP Password, SSL/TLS, Private Key and Digital Certificate. SDNP Certification Authority, LINUX operating system tools for Registrars, SSL, HTTP Session 7 15:15 - 16:30 * Conducting EPP connections - Registrar / Client Side - Practical / Demo EPP clients, fred-client - Download, Configure, Connect, XML, fred-client as backend of registrar website, security * Building your own EPP client * Transferring your current .mw domains to you to manage as a Registrar over EPP connections Session 8 16:30 - 170:0 Workshop evaluation 17:00 - 17:30 Closure of Workshop Malawi SDNP Coordinator, P.O. Box 31762, Chichiri, Blantyre 3, Malawi NIC.MW & .mw ccTLD: http://www.registrar.mw Tel: +265-(0)-1-874979 Cell: +265-(0)-888-824787 E-Mail: domains(a)registrar.mw http://www.registrar.mw/registrars.php --- This email has been checked for viruses by AVG. http://www.avg.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. The following section of this message contains a file attachment prepared for transmission using the Internet MIME message format. If you are using Pegasus Mail, or any other MIME-compliant system, you should be able to save it or view it from within your mailer. If you cannot, please ask your system administrator for assistance. ---- File information ----------- File: hts_1.PNG Date: 9 Apr 2018, 18:59 Size: 7433 bytes. Type: Unknown The following section of this message contains a file attachment prepared for transmission using the Internet MIME message format. If you are using Pegasus Mail, or any other MIME-compliant system, you should be able to save it or view it from within your mailer. If you cannot, please ask your system administrator for assistance. ---- File information ----------- File: hts_2.JPG Date: 9 Apr 2018, 18:59 Size: 8575 bytes. Type: Unknown The following section of this message contains a file attachment prepared for transmission using the Internet MIME message format. If you are using Pegasus Mail, or any other MIME-compliant system, you should be able to save it or view it from within your mailer. If you cannot, please ask your system administrator for assistance. ---- File information ----------- File: hts_3.PNG Date: 9 Apr 2018, 18:59 Size: 15205 bytes. Type: Unknown

7 let, 9 měsíců

← Newer
1
...
6
7
8
9
10
11
12
...
41
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

fred-users