fred-users

fred-users@lists.nic.cz

1 participants
407 discussions

by patrick

Hello Team, Am getting this error whenever I open daphine. Please share with me your experience to get this sorted. Error: Error: CORBA object could not be found! Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/fred_webadmin/exposed.py", line 42, in _wrapper return view_func(*args, **kwd) File "/usr/lib/python2.7/dist-packages/fred_webadmin/controller/adif.py", line 271, in login self._fill_session_data(form, user, corba_session_string) File "/usr/lib/python2.7/dist-packages/fred_webadmin/controller/adif.py", line 229, in _fill_session_data cherrypy.session['RecordsStatement'] = corba_obj.getObject('RecordStatement', 'Registry.RecordStatement.Server') File "/usr/lib/python2.7/dist-packages/fred_webadmin/corba.py", line 109, in getObject return self.getObjectUsingContext(self.context_name, name, idltype) File "/usr/lib/python2.7/dist-packages/fred_webadmin/corba.py", line 98, in getObjectUsingContext obj = self.context.resolve(cosname) File "/usr/lib/python2.7/dist-packages/CosNaming_idl.py", line 239, in resolve return self._obj.invoke("resolve", _0_CosNaming.NamingContext._d_resolve, args) NotFound: CosNaming.NamingContext.NotFound(why=missing_node, rest_of_name=[CosNaming.NameComponent(id='RecordStatement', kind='Object')])

2 roky, 3 měsíce

Web Whois Functionality

by patrick

Dear fred users community, We have been trying to configure web whois after we have upgraded fred database. We have been receiving *Bad Request 500 error*. Please ,we request to get assistance from fred users community. Apache access logs; *tail -f access.log* 129.227.134.6 - - [14/Nov/2022:11:04:23 +0300] "GET /whois HTTP/1.1" 200 1524"https://www.google.com/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5106.0 Safari/537.36 Edg/104.0.1287.1" 196.216.162.82 - - [14/Nov/2022:11:04:44 +0300] "POST /whois/ HTTP/1.1" 302 5081"https://whois.tznic.or.tz/whois" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36" 196.216.162.82 - - [14/Nov/2022:11:04:44 +0300] "GET /whois/object/pns.co.tz/ HTTP/1.1" 500 330"https://whois.tznic.or.tz/whois" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36" 216.144.248.18 - - [14/Nov/2022:11:05:20 +0300] "HEAD / HTTP/1.1" 302 4943"https://whois.tznic.or.tz/" "Mozilla/5.0+(compatible; UptimeRobot/2.0;http://www.uptimerobot.com/)" 216.144.248.18 - - [14/Nov/2022:11:05:21 +0300] "HEAD /whois HTTP/1.1" 200 587"https://whois.tznic.or.tz/" "Mozilla/5.0+(compatible; UptimeRobot/2.0;http://www.uptimerobot.com/)" 35.246.2.112 - - [14/Nov/2022:11:08:11 +0300] "GET /rdap/domain/kariakooexpress.tz HTTP/1.1" 200 7979 "-" "GuzzleHttp/6.5.5 curl/7.29.0 PHP/5.6.40" 129.227.134.6 - - [14/Nov/2022:11:09:17 +0300] "GET / HTTP/1.1" 302 5014"https://www.google.com/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5106.0 Safari/537.36 Edg/104.0.1287.1" 129.227.134.6 - - [14/Nov/2022:11:09:18 +0300] "GET /whois HTTP/1.1" 200 1522"https://www.google.com/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5106.0 Safari/537.36 Edg/104.0.1287.1" 129.227.134.6 - - [14/Nov/2022:11:09:20 +0300] "POST /whois/ HTTP/1.1" 302 355"https://whois.tznic.or.tz/whois" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5106.0 Safari/537.36 Edg/104.0.1287.1" 129.227.134.6 - - [14/Nov/2022:11:09:20 +0300] "GET /whois/object/duhosting.co.tz/ HTTP/1.1" 500 335"https://whois.tznic.or.tz/whois" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5106.0 Safari/537.36 Edg/104.0.1287.1 *tail -f error.log* [Mon Nov 14 11:07:21.467113 2022] [:error] [pid 6071] (32)Broken pipe: [client 127.0.0.1:52854] Error when sending response [Mon Nov 14 11:07:23.469423 2022] [:error] [pid 6068] [client 127.0.0.1:52888] Whois usage error: Too many search keys. [Mon Nov 14 11:07:23.469608 2022] [:error] [pid 6068] (32)Broken pipe: [client 127.0.0.1:52888] Error when sending response [Mon Nov 14 11:07:25.472207 2022] [:error] [pid 5964] [client 127.0.0.1:52910] Whois usage error: Too many search keys. [Mon Nov 14 11:07:25.472387 2022] [:error] [pid 5964] (32)Broken pipe: [client 127.0.0.1:52910] Error when sending response [Mon Nov 14 11:07:27.474728 2022] [:error] [pid 6027] [client 127.0.0.1:52920] Whois usage error: Too many search keys. [Mon Nov 14 11:07:27.474881 2022] [:error] [pid 6027] (32)Broken pipe: [client 127.0.0.1:52920] Error when sending response [Mon Nov 14 11:07:28.476112 2022] [:error] [pid 5960] [client 127.0.0.1:52922] Whois usage error: Too many search keys. [Mon Nov 14 11:07:28.476306 2022] [:error] [pid 5960] (32)Broken pipe: [client 127.0.0.1:52922] Error when sending response [Mon Nov 14 11:07:36.321257 2022] [:error] [pid 5968] [client 192.3.251.168:36330] Request is not terminated by <CR><LF> *tail -f fred-webwhois.log* [pid: 4885|app: 0|req: 14014/29877] 154.74.144.3 () {76 vars in 1392 bytes} [Mon Nov 14 01:51:10 2022] GET /whois => generated 2564 bytes in 26 msecs (HTTP/1.1 200) 6 headers in 317 bytes (2 switches on core 0) [pid: 4885|app: 0|req: 14015/29878] 154.74.144.3 () {82 vars in 1520 bytes} [Mon Nov 14 01:51:12 2022] POST /whois/ => generated 0 bytes in 2 msecs (HTTP/1.1 302) 6 headers in 194 bytes (1 switches on core 0) [pid: 4885|app: 0|req: 14016/29879] 154.74.144.3 () {76 vars in 1468 bytes} [Mon Nov 14 01:51:12 2022] GET /whois/object/zanzibeer.tz/ => generated 27 bytes in 33 msecs (*HTTP/1.1 500*) 5 headers in 157 bytes (1 switches on core 0) [pid: 4885|app: 0|req: 14017/29880] 216.144.248.18 () {66 vars in 1138 bytes} [Mon Nov 14 01:55:21 2022] HEAD /whois => generated 2564 bytes in 26 msecs (HTTP/1.1 200) 6 headers in 317 bytes (1 switches on core 0) [pid: 4885|app: 0|req: 14018/29881] 216.144.248.18 () {66 vars in 1138 bytes} [Mon Nov 14 02:00:21 2022] HEAD /whois => generated 2564 bytes in 26 msecs (HTTP/1.1 200) 6 headers in 317 bytes (1 switches on core 0) [pid: 4885|app: 0|req: 14019/29882] 129.227.134.6 () {78 vars in 1489 bytes} [Mon Nov 14 02:03:25 2022] GET /whois => generated 2564 bytes in 25 msecs (HTTP/1.1 200) 6 headers in 322 bytes (1 switches on core 0) [pid: 4885|app: 0|req: 14020/29883] 129.227.134.6 () {88 vars in 1736 bytes} [Mon Nov 14 02:03:31 2022] POST /whois/ => generated 0 bytes in 47 msecs (HTTP/1.1 302) 6 headers in 194 bytes (1 switches on core 0) [pid: 4885|app: 0|req: 14021/29884] 129.227.134.6 () {82 vars in 1670 bytes} [Mon Nov 14 02:03:31 2022] GET /whois/object/mail.tz/ => generated 27 bytes in 60 msecs (*HTTP/1.1 500*) 5 headers in 162 bytes (2 switches on core 0) [pid: 4885|app: 0|req: 14022/29885] 129.227.134.6 () {80 vars in 1578 bytes} [Mon Nov 14 02:03:35 2022] GET /whois => generated 2564 bytes in 24 msecs (HTTP/1.1 200) 6 headers in 322 bytes (2 switches on core 0) [pid: 4885|app: 0|req: 14023/29886] 129.227.134.6 () {78 vars in 1558 bytes} [Mon Nov 14 02:04:23 2022] GET /whois => generated 2564 bytes in 22 msecs (HTTP/1.1 200) 6 headers in 322 bytes (2 switches on core 0) [pid: 4885|app: 0|req: 14024/29887] 196.216.162.82 () {88 vars in 1746 bytes} [Mon Nov 14 02:04:44 2022] POST /whois/ => generated 0 bytes in 2 msecs (HTTP/1.1 302) 6 headers in 191 bytes (2 switches on core 0) [pid: 4885|app: 0|req: 14025/29888] 196.216.162.82 () {82 vars in 1685 bytes} [Mon Nov 14 02:04:44 2022] GET /whois/object/pns.co.tz/ => generated 27 bytes in 40 msecs (*HTTP/1.1 500*) 5 headers in 157 bytes (2 switches on core 0) Thank you, Patrick

2 roky, 3 měsíce

just for Denzell - (Fwd) DENZELL: exact error ? - Re: Fred Installation Problems on Ubuntu 22.04

by Dr Paulos Nyirenda

Apologies, this was meant for Denzell only, a collegaue on .mw at Malawi SDNP, who is attempting to install and get familiar with FRED. Regards, Paulos ------- Forwarded message follows ------- From: "Dr Paulos Nyirenda" <paulos(a)sdnp.org.mw> To: A mailing list for users and developers of FRED registry system <fred-users(a)lists.nic.cz> Date sent: Thu, 10 Nov 2022 18:20:16 +0200 Subject: DENZELL: exact error ? - Re: Fred Installation Problems on Ubuntu 22.04 Copies to: Dr Paulos Nyirenda <paulos(a)sdnp.org.mw> Priority: normal On 10 Nov 2022 at 17:26, Denzell Yonah wrote: > > Hi Jaromir, > Please advise on the correct version of Ubuntu to use. > I am still having trouble with the repo: archive.nic.cz/ubuntu. I am > still getting a 404 error with the repo thus failing to download > fred with: sudo apt-get install fred. Regards, Denzell, It might help for you to copy the exact error into the message so that people on the other side have a chance to analyse it. Have you tried that ? Regards, PC ============================= Dr Paulos B Nyirenda NIC.MW & .mw ccTLD http://www.nic.mw SDNP: http://www.sdnp.org.mw Tel: +265-(0)-882 089 166 Cell: +265-(0)-888-824787 WhatsApp: +265-(0)-887386433 > > Denzell Yonah > Internet Technician > Malawi SDNP > > > > > > > > > > Tel: 882 089 166 | Cell: 888 844 657 > > > > > domains(a)registrar.mw > > > > > http://www.nic.mw | http://www.registrar.mw > > > > > P.O. Box 31762, Malawi SDNP, Chichiri, Blantyre > > > > > > > > > On 11/10/22 14:55, Jaromir Talir wrote: > > I meant there is a new URL for the script in the documentation. > You need to call: wget -O fred-ubuntu-install.sh > https://fred.nic.cz/public/media/1665476288/113/ > > Old URL doesn't work anymore. > > Regards, > Jaromir > > On Thu, 2022-11-10 at 14:50 +0200, Denzell Yonah wrote: > > > Hi Jaromir, > I am still receiving the very same errors as before. > Regards, > > Denzell Yonah Internet Technician Malawi SDNP Tel: 882 089 166 > | Cell: 888 844 657 domains(a)registrar.mw http://www.nic.mw | > http://www.registrar.mw P.O. Box 31762, Malawi SDNP, Chichiri, > Blantyre > > On 11/10/22 14:09, Jaromir Talir wrote: > > > > Hi Denzell, > > there was a fix in the script and URL was not changed in > documentation. > Sorry for confusion. Correct URL has been put into: > https://fred.nic.cz/documentation/html/AdminManual/Installation/ > Bi nsUbuntu.html#installation-script > > Let me know if it will not work now. > > Regards, > Jaromir > > On Wed, 2022-11-09 at 10:28 +0200, Denzell Yonah wrote: > > > > Hello Fred Users, > I am having trouble downloading the installation script using: > 'wget -O fred-ubuntu-install.sh > https://fred.nic.cz/public/media/1568014036/56/'. It produces a > 404 error: 'HTTP request sent, awaiting response... 404 Not > Found'. On trying to install from source tarballs, adding > repositories 'add- apt-repository "deb > http://archive.nic.cz/ubuntu $(lsb_release - sc) main"' and > 'add-apt-repository "deb http://archive.nic.cz/private > $(lsb_release -sc) main"' a "no release file/404" error for the > first repo and "is not signed/forbidden" for the latter. Please > help on how I can work this out. > _______________________________________________ fred-users > mailing list -- fred-users(a)lists.nic.cz To unsubscribe send an > email to fred-users-leave(a)lists.nic.cz > > > _______________________________________________ > fred-users mailing list -- fred-users(a)lists.nic.cz > To unsubscribe send an email to fred-users-leave(a)lists.nic.cz > > > _______________________________________________ > fred-users mailing list -- fred-users(a)lists.nic.cz > To unsubscribe send an email to fred-users-leave(a)lists.nic.cz > > > _______________________________________________ > fred-users mailing list -- fred-users(a)lists.nic.cz > To unsubscribe send an email to fred-users-leave(a)lists.nic.cz > -- This email has been checked for viruses by AVG antivirus software. www.avg.com ------- End of forwarded message -------

2 roky, 3 měsíce

Fred Installation Problems on Ubuntu 22.04

by Denzell Yonah

Hello Fred Users, I am having trouble downloading the installation script using: 'wget -O fred-ubuntu-install.sh https://fred.nic.cz/public/media/1568014036/56/'. It produces a 404 error: 'HTTP request sent, awaiting response... 404 Not Found'. On trying to install from source tarballs, adding repositories 'add-apt-repository "deb http://archive.nic.cz/ubuntu $(lsb_release -sc) main"' and 'add-apt-repository "deb http://archive.nic.cz/private $(lsb_release -sc) main"' a "no release file/404" error for the first repo and "is not signed/forbidden" for the latter. Please help on how I can work this out. -- Regards, Denzell Yonah Internet Technician Malawi SDNP Tel: 882 089 166 <tel:882 089 166> | Cell: 888 844 657 <tel:888 824 787> domains(a)registrar.mw <mailto:domains@registrar.mw> http://www.nic.mw | http://www.registrar.mw <http://www.nic.mw | http://www.registrar.mw> P.O. Box 31762, Malawi SDNP, Chichiri, Blantyre

2 roky, 3 měsíce

Removing a DNS entry in server list for a zone

by Gregory Bernard

Hello Fred-Users, I have a little question, we need to change an existing NS record for some zones. On the user guide there is a clear reference on how to add an entry : https://fred.nic.cz/documentation/html/AdminManual/RegistryInitialization.h… With couple of exemples : fred-admin --zone_ns_add --zone_fqdn=cz --ns_fqdn=a.ns.nic.cz fred-admin --zone_ns_add --zone_fqdn=cz --ns_fqdn=b.ns.nic.cz --addr=1.2.3.4 But I need first to remove an old entry and I don’t see any « fred-admin —zone_ns_rm —ns_fqdn=… » or equivalent command. So what would be the right way to first remove an old entry then add a new one ? Thanks for your help. Sincerely yours.

2 roky, 6 měsíců

Hiding contact address not allowed

by jiri.kuchta＠email.cz

Hi, I've came accross a case where calling EPP contact:update command with disclosure settings {"flag": "n", "data": ["addr"]} returns "Operation not permitted" for contact with "identifiedContact" flag. According to rules for hiding contact address in .CZ (https://háčkyčárky.cz/files/nic/doc/Pravidla_Technicke_Komunikace_20191115.…) this should be allowed. Can you please confirm the rules are still valid? Thank you.

2 roky, 9 měsíců

FRED bad exDate result in poll

by Dr Paulos Nyirenda

FRED bad exDate result in poll ========================== We are seeing a different (bad) result of exDate in poll messages compared to that in the WHOIS or in the info_domain EPP command result for some domains follwoing a database change, please allow me to explain. At least one registrar in the past year has requested a roll back of the expiry date of a .mw domain following a mistake by staff of the registrar who put more years on the domain renew than what was paid for. We normally resist rolling back the expiry date but in these cases we had no choice. What was done was to run an SQL command on postgres to change the expiry dates say from 2023 to 2022. What we have noted is that when this is done the WHOIS will report the correct 2022 expiry date, the info_domain EPP command reports the same 2022 expiration date but when the "fred-admin --object_regular_procedure" is excuted and then we run the "poll req" EPP command, it still gives the 2023 exDate Would be interesting to find out why this is the case. This is confusing the registrar managing such a domain and we would like to ask that these dates should be the same in any future FRED uogarde. Or is there a better way of rolling back the expiry date for a domain that has mistakenly been given more life years than wanted ? Regards, Paulos ============================= Dr Paulos B Nyirenda NIC.MW & .mw ccTLD http://www.nic.mw SDNP: http://www.sdnp.org.mw Tel: +265-(0)-882 089 166 Cell: +265-(0)-888-824787 WhatsApp: +265-(0)-887386433 -- This email has been checked for viruses by AVG. https://www.avg.com

2 roky, 10 měsíců

fred plugin to intergrate with wisecp

by MUTUTU COMPUTERS

Hallow Team, I am using wisecp wisecp.com as my billing system and domain/hosting managment system. we do register our country domain .tz using fred-client. Now we wanted to develop a plugin that will integrate wisecp with fred-client to register and manage .tz domains on wisecp system. Is there is anyone who can assist to develop the plugin here, we can discuss way forward to accomplish this Many thanks Whatsapp +255759234610 -- MUTUTU COMPUTERS +254 111 583238

2 roky, 11 měsíců

Log4j vulnerability audit

by Kelvin Truong

Hi FRED users, Following the Log4j reports, we performed an audit on our FRED deployment and couldn’t find residence of Log4j 2.x. At the same time we don’t remember being ever asked to install JDK when performing the FRED setup initially. Looking for affirmation from the esteemed community here if our findings are accurate? Many thanks! Kelvin

3 roky, 1 měsíc

Re: SSL certs for EPP-client

by Dr Paulos Nyirenda

On 18 Nov 2021 at 11:29, bsd(a)todoo.biz wrote: > Hello Dr. Nyirenda, > > Thanks a lot for your help. > > Do you by any chance have the formula that you are using to create or > renew your client side certificates? , What is your TLD ? We are using openssl and I do not think there is a "formula" as such > We are fighting because one of our engineer has left the company and > did´t properly document things. One certificate has expired in > july, we didn´t notice until server was rebooted... Now it is a bit > emergency. One of the ways could be for you to create your own CA, put the CA certificate into the FRED config on the server side and using that issue a new certificate to the registrar. Regards, PC ============================= Dr Paulos B Nyirenda NIC.MW & .mw ccTLD http://www.nic.mw SDNP: http://www.sdnp.org.mw Tel: +265-(0)-882 089 166 Cell: +265-(0)-888-824787 WhatsApp: +265-(0)-887386433 > > > Sincerely yours. > > Le 18 nov. 2021 à 08:54, Dr Paulos Nyirenda <paulos(a)sdnp.org.mw > > a écrit : > > On 16 Nov 2021 at 14:41, bsd(a)todoo.biz wrote: > > Hello, > > I was wondering if the SSL certs which are created to authenticate > EPP requests will need to be bound to a CA or if they only needed > to be created as plain Cert + Key. > > In fred-client.conf - there only seems to have an : > > ssl_cert = %(dir)s/cert.xxx.pem > ssl_key = %(dir)s/key.unenc.xxx.pem > > If I remember correctly, this is enough on the client side. > > No sign of CA. > > Also if I remember correctly, the CA certificate corresponding to > your client certificate is only needed to be installed on the > FRED server side for your EPP client > > Hope this helps. > > Regards, > > Paulos > ============================= > Dr Paulos B Nyirenda > NIC.MW & .mw ccTLD > http://www.nic.mw > SDNP: http://www.sdnp.org.mw > Tel: +265-(0)-882 089 166 > Cell: +265-(0)-888-824787 > WhatsApp: +265-(0)-887386433 > -- This email has been checked for viruses by AVG. https://www.avg.com

3 roky, 3 měsíce

← Newer
1
2
3
4
5
6
7
8
9
...
41
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

fred-users